| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
PG_WRITEABLE are already cleared by vm_page_protect().
|
|
|
|
|
|
|
|
| |
buggy for fifos, and no one seems to have investigated its behaviour
on other types of files. It has been broken since the Lite2 merge
in rev.1.54.
Nagged about by: Brian Feldman (green@unixhelp.org)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I added a FICL_TRACE-conditioned trace facility based on "see".
It is ugly because words' functions are almost all static, and ficlExec,
where the trace has to be located, can't get their pointers. So, #ifdef
this staticization, and add most of see's body into ficlExec. Duplication
of code, uglyness, etc. But it is cleanly #ifdef'ed, and works like a
charm.
It does not provide "step" facility, though, just trace. It is
tunable at run-time through "trace!". If anyone (most likely me :) ever
wants a step facility, I'll add it. Should be easy.
PR: bin/9652
Submitted by: "Daniel C. Sobral" <dcs@newsguy.com>
|
|
|
|
|
|
| |
to use the vm_page_dirty() inline.
The inline can thus do sanity checks ( or not ) over all cases.
|
|
|
|
|
| |
PR: bin/9651
Submitted by: "Daniel C. Sobral" <dcs@newsguy.com>
|
|
|
|
|
|
|
|
|
|
| |
vm_page_rename(), but never pulled the page off PQ_CACHE if it was on
PQ_CACHE. Dirty pages in PQ_CACHE are not allowed and a KASSERT was
added in -4.x to test for this... and got hit.
In -4.x, vm_page_rename() automatically dirties the page. This commit
also has it deal with the PQ_CACHE case, deactivating the page in that
case.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FICL's TYPE copies the counted string to HERE, as abial has
remarked. Answering to abial's question, this is NOT garanteed to have
enough space.
...
We have dynamic memory. Even before memory-alloc got in, we
already had dynamic memory. Use it, then! (ficlMalloc is sysdep, so I
suppose that's why it was not used for TYPE; ficl is probably designed
to work without a working ficlFree).
Submitted by: "Daniel C. Sobral" <dcs@newsguy.com>
|
| |
|
|
|
|
|
|
| |
without VINUMDEBUG
Submitted-by: peter
|
|
|
|
|
| |
not have a bug in it, but the last commit did make it more readable so
we are keeping it.
|
|
|
|
|
|
|
| |
values. The 'int' return value for the procedure was never used and
not well defined in any case when there are mixed errors on pages, so
it has been removed. vm_pager_put_pages() and associated vm_pager
functions now return void.
|
|
|
|
| |
cache.
|
|
|
|
| |
while trying to free memory.
|
|
|
|
|
|
| |
and that vinum should be started as a kld.
Tripped-over-by: many people
|
|
|
|
| |
on a PG_BUSY page, due to a bug in its sequencing of a conditional.
|
|
|
|
| |
checking for this condition while it tried to free cache pages. Fixed.
|
|
|
|
| |
PG_BUSY stupidity.
|
|
|
|
| |
but the bit should definitely be cleared.
|
|
|
|
| |
vm_object_pmap_copt_1() now, apparently.
|
|
|
|
|
| |
page is still busy after all the hell vm_fault goes through.. it is
supposed to be, and printf() if it isn't. don't panic, though.
|
|
|
|
|
|
|
| |
> 0 b_validend. This will screw up small-writes, causing lots of
little writes out the network.
We will assume that NFS handles B_CACHE properly.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Implement a new variable 'root_disk_unit' which supersedes
'num_ide_disks' and makes it possible to explicitly set the
root device unit number regardless of type considerations.
bootinfo.c
If we can't calculate a dev_t for the root disk, complain and
don't proceed to boot with an invalid boot device.
|
|
|
|
| |
guess this value well in anything other than the simplest of situations.
|
|
|
|
| |
Prompted by: gcc warnings when compiling /sbin/ipfw
|
| |
|
| |
|
|
|
|
| |
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> (partly)
|
|
|
|
|
| |
PR: 9445
Noticed by: Ying-Chieh Liao <ijliao@Terry.Dorm10.NCTU.edu.tw>
|
|
|
|
|
|
|
|
| |
and MSP34xx Audio chip. Fixed i2c read error.
Hauppauge supplied details of new Tuner Types.
Added tuner type 0x1a.
Danny Braniss <danny@cs.huji.ac.il> submitted Bt878
AverMedia detection with PCI subsystem vendor id.
|
|
|
|
| |
Updated to support Hauppauge IR Remote Control
|
| |
|
|
|
|
|
| |
- Describe options for the vga driver.
Reviewed by: bde
|
|
|
|
|
| |
have any operational effects other then to make the code in question
a little faster. Also added a more involved comment.
|
|
|
|
|
| |
of PQ_CACHE. Add comments explaining what it accomplishes and its
limitations.
|
|
|
|
|
|
|
|
|
|
| |
patch. lf can't be dereferenced after the unload attempt, in case it
was freed. Instead, decrement first and back it out if the unload failed.
This should be relatively immune to races caused by the user since the
userref count will be zero for the duration of the actual unloading and
will stop further kldunload attempts.
Submitted by: Ustimenko Semen <semen@iclub.nsu.ru>
|
|
|
|
| |
kernel where #include "filename.h" has been disabled.
|
|
|
|
| |
the other is a new file.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Make TIB handling use buffer size to conform with ANS Forth.
Add ANS MEMORY-ALLOC word set.
See the PRs for extensive details.
PR: kern/9412 kern/9442 kern/9514
Submitted by: PRs from Daniel Sobral <dcs@newsguy.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
help.common
interp.c
Rename the 'source' command to 'include' in order to avoid conflict
with the ANS Forth command of the same name. (kern/9473)
interp_forth.c:
Changes from kern/9412 (EXCEPTION word), kern/9442 (TIB buffer
sizing) and an improved version of kern/9460 (set
version numbers).
load_aout.c:
Trim some obsolete #if 0'ed cruft.
pnp.c:
Tidy the pnpscan output, turn off the module scanning until we
sort out how to do it right.
PR: kern/9412 kern/9442 kern/9460 kern/9473
Submitted by: PRs from Daniel Sobral <dcs@newsguy.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Suggested by: fenner
Original complaint: Shiva Shenoy <Shiva.Shenoy@yagosys.com>
|
|
|
|
|
|
|
| |
of the CRC as the multicast hash table bit, not the lower six bits. Plus
we have to flip on all bits in the table for multicast mode.
Pointed out by: Kazushi SUGYO <k-sugyou@nwsl.mesh.ad.jp>
|
|
|
|
|
|
|
| |
that the BTX code can be regarded as stable: there are no associated
code changes.
Suggested by: obrien
|