| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
| |
PR: docs/58437
Submitted by: Joachim Strombergson
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
the denormal/unnormal trap, is not a standard IEEE trap. We did
not exclude it from being returned by fpgetmask(), nor did we make
sure that fpsetmask() didn't clobber it. Since the non-IEEE trap
is not part of fp_except_t, users of ifpgetmask()/fpsetmask() would
be confronted with unexpected behaviour, one of which is a SIGFPE
for denormal/unnormal FP results.
This commit makes sure that we don't leak the denormal/unnormal mask
bit in fp_except_t and also that we don't clobber it.
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
|
|
|
|
|
| |
as [0] and replace it with the ISO way of writing []. This has caused
warnings with WARNS=6.
|
| |
|
|
|
|
|
|
| |
indication of lack of media.
Tripped up: peter
|
|
|
|
| |
so high phy error rates on a 5212 don't cause rx overruns
|
| |
|
|
|
|
|
| |
PR: docs/58355
Submitted by: Simon Barner <barner@in.tum.de>
|
|
|
|
|
| |
Until we can have perfect knowledge that all callers above us think it's okay
for us to sleep, releasing *our* locks of course, we don't dare try and sleep.
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
|
|
|
| |
- change node-local to interface-local.
- better error handling of address-to-scope mapping.
- use in6_clearscope().
Obtained from: KAME
|
|
|
|
| |
Approved by: krion (mentor)
|
|
|
|
|
|
| |
vm_page_set_validclean(). (This function reads and modifies the
vm page's valid field, which is synchronized by the lock on the
containing vm object.)
|
|
|
|
|
| |
1.183 -> 1.184 hardware/common/dev.sgml
1.640 -> 1.644 relnotes/common/new.sgml
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in connection with Marvell based SATA->PATA dongles.
The problem was caused by a combination of things working
together to make it hard to spot...
The ATA driver has always started the ATA command, then build
the SG list for DMA and then finally started the DMA engine.
While this is according to specs, it poses a potential
problem as some controllers apparently do not allow for unlimitted
time between starting the ATA command and starting the DMA engine.
At about the same time as ATAng was committed there were lots
of other changes applied, some of which was locking in parts
that causes the busdma load functions to take significantly
longer to load the SG list.
This pushed the time spent between starting the ATA command and
starting the DMA engine over the hill for some controllers
(especially the Silicon Image DS3112a) and caused what looked
like lost interrupts.
The solution is to get all the SG list work or rather all
busdma related stuff done before we even try to start anything.
This has the nice side effect of seperating busdma out the
way it should be, so the working of the ATA machinery is not
cluttered up with busdma droppings, making the code easier
to read and understand.
|
|
|
|
|
|
| |
instead use 14.4kbps and faster modems as examples. Separate line
speed and baud rate and be careful when talking of one verses the
other.
|
|
|
|
| |
Suggested by: njl
|
|
|
|
|
| |
from CTLFLAG_RD to CTLFLAG_RDTUN so that sysctl(8) can provide
more useful error messages.
|
|
|
|
| |
user has attempted to write to a read only, tunable value.
|
|
|
|
|
|
|
|
| |
sysctl that a given variable is tunable.
Also added is CTLFLAG_RDTUN, which is CTLFLAG_RD|CTLFLAG_TUN; TUN does
not always imply read-only, so RDTUN should be used where RD was used
before.
|
| |
|
|
|
|
| |
becuase bp->b_blkno is ignored now.
|
|
|
|
|
| |
stops users being able to cause setgroups to clobber the kernel stack by
copying in data past the end of the linux_gidset array.
|
|
|
|
|
|
| |
and then some of its Cyrix inheritance.
Set the max_iosize for the Cyrix to 63K as the SC1100.
|
|
|
|
| |
Remove trailing whitespace.
|
|
|
|
| |
Use newspeak functions definitions.
|
|
|
|
|
| |
on it for the last 15 hours with no signs of problems. It gives a small
(1%) gain on buildworld since pipe_read/pipe_write are already free of Giant.
|
|
|
|
|
|
|
|
| |
for dev_strategy() use.
Retire bio_driver[12] (aliases for b_io.bio_driver[12]) these fields are
reserved for device driver use and can as such never have any interest
in the buf end of things.
|
|
|
|
| |
away.
|
|
|
|
|
|
|
|
|
|
|
|
| |
rate is how fast modems exchange symbols. Bit rate is how many bits
per second the serial port nominally communicates at. Try to use bit
rate consistently where that's what is ment. The default data rate is
now 9600 baud. 300 baud being default pre-dates 4.4-LITE1. Document
that tip doesn't respect the system default rate for a given channel.
Sorry guys, but no ucbvax, kremvax or kgbvax added to the example.
Noted by: bde
|
|
|
|
|
| |
the backing store is at a fixed address, there's no need for a
per-thread variable.
|
| |
|
|
|
|
| |
livelock problem
|
|
|
|
|
| |
'kilo' or 'mega' with appropriate suffix instead of filling the field
with stars.
|
|
|
|
| |
Reported by: pawel.worach@nordea.com
|
|
|
|
| |
Reviewed by: imp
|
| |
|
|
|
|
|
|
|
| |
facilitates synchronization of the vm page's valid field using the
vm object's lock.)
Suggested by: tegge
|
| |
|
|
|
|
| |
Obtained from: KAME
|