| Age | Commit message (Collapse) | Author |
|---|
|
noticed by naddy@, tested by me, ok deraadt@
|
|
|
|
messages for devices using prefetchable memory sitting behind bridges.
|
|
|
|
by options in ~/.ssh/config. From Dan Peterson.
|
|
|
|
the ramdisk
|
|
uvm_km deals with kernel memory which is either part of one of the
kernel maps, or the main kernel object (a uao). If on km_pgremove we hit
a busy page, just sleep on it, if so there's some async io (and that is
unlikely). we can remove the check for uvm_km_alloc1() for a released page
since now we will never end up with a removed but released page in the kernel
map (due to the other chunk and the last diff).
ok ariane@. Diff survived several make builds, on amd64 and sparc64,
also forced paging with ariane's evil program.
|
|
Now, the PG_ RELEASED flag currently has two (maybe three) uses. The
valid one is for use with async io where we want to free the page after
we've paged it out. The other ones are "oh i'd like to free this, but
someone else is playing with it". It's simpler to just sleep on the
damned page instead and stop the fiddling.
First step does uao's: in uao_detach, sleep on the object and free it
when we're clean, instead of setting a flag so it's freed after. In
uao_flush, do the same. Change the interation over the object in flush
so that we don't have to add marker pages or other such voodoo to the
list when we sleep (netbsd did that when they had a similar diff), just
use the hash always. We can now change uao_releasepg() to just free the
page, and not bother with the KILLME stuff. When the other objects are
fixed this hook will vanish.
Much discussion with art@ over the idea, and ariane@ over this specific
diff. As mentioned, this one is based loosely on a similar idea in
netbsd.
Been in my tree for a while, survived many make builds, etc, and forcing
paging using ariane's evil program.
ok ariane@, beck@.
|
|
|
|
|
|
|
|
sleep on them (and otherwise ignore them) sleep on the pointer to the
{aiodoned,pagedaemon}_proc members, and nuke the two extra words.
"no objections" art@, ok beck@.
|
|
- need to explicitly bring bridge0 up; from mpf
- final example needs "link2"; from bsd
ok mpf
|
|
while here, recommend to set variables in *.local, not in root/crontab
(in preparation for the upcoming next_part diff)
ok jmc@
|
|
the type we bind to an iommu or a GART is paddr_t, by definition, on the
other hand, the type we get out of it is not a vaddr_t, it's bus_addr_t.
fix up sparc64 iommu, amd64 iommu and the sg_dma backedn that uses it to
realise this.
ok kettenis@
|
|
|
|
reference the code in global envy_card structures. Allows the same
mixer code to be shared across differents cards. Will ease adding
codec-specific knobs when adding support for new cards.
|
|
|
|
|
|
|
|
and fix two pastos in the printf(1) reporting bad group IDs;
ok okan@
|
|
ok deraadt@
|
|
them along when we attach pci(4). Simplify the rbus code by using extents
too.
|
|
this case by choosing the interrupt that corresponds to the PCI function.
Makes the second PCMCIA slot work.
|
|
|
|
ok deraadt@
|
|
controls later. Also stop using ``next'' and ``prev'' pointers,
since they make impossible exposing ``source'' knobs for streams
that do not have ``gain'' knobs. This implies renaming ``xxx.source''
knobs to ``xxx_source''. Besides that, no behaviour change.
|
|
|
|
resources to cards not configured by the PROM. There are still some
shortcomings, but this is a good start.
Tested on IP35 with an fxp(4).
|
|
|
|
while here, remove the misleading shbang and an unused variable
and add the missing cross reference to ac(8)
ok sthen@ jmc@
|
|
also make the %'s add up to 100 again, which was part of the problem
ok krw otto
|
|
|
|
partition info into one string separated by the lexically low value
'!' char and sorting those strings. This eliminates an inner loop
over partition info. No user visible change.
|
|
simply calling iommu_dvma_unload(). Solution suggested by oga@.
While there, also unwrap a line that isn't long enough to need wrapping.
|
|
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.
Found by and ok kettenis@
|
|
should not stop the spoofing process. Setting 'wander' means when
we are done with this MBR, read the next one.
Problem noted and fix tested by Nick Guenther.
ok weingart@ (I think), deraadt@
|
|
the ftp server you probably want to use. Some XXX's in the code still;
please report issues to me.
ok krw
|
|
they are discovered rather than keeping a list and appending it to
the end of the fstab. No impact unless you configure extra swap
partitions.
ok deraadt@
|
|
was incorrectly being treated as signed. ok miod@
|
|
the next unit K->M->G. ok deraadt@
|
|
|
|
|
|
|
|
|
|
information, instead of trying to attach whatever is defined in the
kernel configuration file.
|
|
but (currently commented out) code makes isp happier on IP27 and IP35, to the
point of seeing disks (but considering them offline so far).
|
|
large window IOTTE.
|
|
|
