| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Also, more closely match the prototypes in sys/rwlock.h and add a BUGS
section.
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
| |
Submitted by: markus
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Use a directory layout that is more akin to the i386 boot layout.
o Create a libat91 for library routines that are used by one or more
of the boot loaders.
o Create bootiic for booting from an iic part.
o Create bootspi for booting from an spi part.
o Optimize the size of many of these routines (especially emac.c). Except
for the emac.c optimizations, all these have been tested.
o eliminate the inc directory, libat91 superceeds it.
o Move linker.cfg up a layer to allow it to be shared.
|
| |
|
|
|
|
|
|
|
|
| |
and the usage message of top, but not to the manpage.
Pointy hat to: keramida
Reminded by: ru
MFC after: 1 week
|
|
|
|
|
|
|
| |
commands to be executed under a different credential.
PR: bin/95777
Submitted by: clsung
|
|
|
|
| |
Security: FreeBSD-SA-06:14.fpu
|
|
|
|
|
|
|
|
| |
for some early starting services from the ports collection
to have their shared objects available before start.
Reviewed by: freebsd-rc (dougb, brooks)
MFC After: 3 days
|
|
|
|
| |
Noticed by: maxim
|
| |
|
|
|
|
|
| |
and pick a bogus geometry if it had so we don't later
get a divide by zero trap.
|
|
|
|
|
| |
update here before we switch to the new f/w loading
framework.
|
| |
|
|
|
|
|
|
|
|
| |
state structure. This field is only for CCBs that are associated with
actions that are occurring on the HBA (i.e., XPT_CONT_IO actions).
This way we also don't get confused when the upstream listener stalls
try and look at a CCB which has already been freed (by CAM).
|
|
|
|
|
|
| |
PR: docs/95059
Submitted by: Jos Backus
MFC after: 4 days
|
|
|
|
|
|
| |
configurations.
Approved by: jhb
|
|
|
|
|
|
|
| |
to reduce the pv_entry_count counter. This was found by Tor Egge. In the
same email, Tor also pointed out the pv_stats problem in the previous
commit, but I'd forgotten about it until I went looking for this email
about this allocation problem.
|
|
|
|
| |
Do not compile out its counter updates if pv entry stats are turned off.
|
|
|
|
| |
merged items.
|
|
|
|
|
|
| |
PR: docs/67893
Submitted by: Chris Pepper, Daniel Gerzo
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
locked. In general the adaptive spinning is similar to the same code
for mutexes with some extra trickiness in rw_wunlock_hard(). Specifically,
even though both wait bits might be set and we might have a turnstile with
at least one waiting thread, there might not be any threads blocked on the
queue we are not waking up (they might all be spinning), and we should
only preserve the waiting flag for the queue we aren't waking up if there
are in fact threads blocked on that queue. Secondly, there might not be
any threads blocked on the queue we have chosen to waken threads from
(there might only be threads blocked on the other queue and the threads
for this queue are all spinning) in which case we disown the turnstile
instead of doing a braodcast and unpend.
|
|
|
|
| |
describe turnstile_disown() and turnstile_empty().
|
|
|
|
|
|
| |
queue on a turnstile is empty.
- Add a turnstile_disown() function that allows a thread to give up
ownership of a turnstile w/o waking up any waiters.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Sync with latest version from NetBSD.
'In order to handle some perl scripts running as daemons, add a
pattern which also matches "`basename $interpreter`: $command" in the
ps listing.'
Approved by: cperciva (mentor)
Obtained from: NetBSD
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
- Add default value in /etc/defaults/rc.conf.
- Add documentation bits to rc.conf(5).
Approved by: cperciva (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
stored in metadata instead of an offset in single disk.
After reboot/crash synchronization process started from a wrong offset
skipping (not synchronizing) part of the component which can lead to data
corrutpion (when synchronization process was interrupted on initial
synchronization) or other strange situations like 'graid3 status' showing
value more than 100%.
Reported, reviewed and tested by: ru
Reported by: Dmitry Morozovsky <marck@rinet.ru>
MFC after: 1 day
|
|
|
|
| |
MFC after: 4 days
|
|
|
|
| |
Submitted by: Alex Lyashkov <umka@sevcity.net>
|
|
|
|
|
|
|
|
|
|
| |
from ports. The effect is that ldconfig is now started right after
mountcritremote. Everything else is left unchanged.
PR: conf/68916
Submitted by: JD Bronson <jd@aurora.org>
Approved by: cperciva (mentor)
MFC after: 1 week
|
|
|
|
| |
kernel option will affect both forwarding methods - classic and fast.
|
|
|
|
|
|
| |
so explicitly constify the mp parameter.
Reviewed by: phk
|
|
|
|
|
|
| |
i915 attachment.
Submitted by: Jonathan Fosburgh <jonathan@fosburgh.org>
|
|
|
|
| |
use -q, not -v.
|
|
|
|
|
|
|
| |
as pcf_ebus and pcf_isa, they should probably be fixed back to pcf),
and bti2c doesn't exist, bktr has smbus or iicbb as children..
Brought to you by: http://people.FreeBSD.org/~jmg/driver.pdf
|
|
|
|
|
|
|
|
| |
use it in places that only care about the write owner instead of
rw_owner() as a baby step towards limited read-lock owner.
- Tidy the code that sets the WAITER flag bits to not duplicate a test
around the atomic operation and the KTR trace in both of the lock
functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
above what's used for fast interrupts, only interrupts with the level of
the interrupt which led to calling intr_fast() (which is used with both
fast and ithread interrupts) are blocked while in that function. Thus
intr_fast() can be preempted by a fast interrupt (which are of a higher
level than ithread interrupts) while servicing an ithread interrupt. This
can lead to a stale pointer to the head of the active interrupt requests
list when back in the ithread interrupt invocation of intr_fast(), in turn
resulting in corruption of the interrupt request lists and consequently
in a panic. Solve this be turning off interrupts in intr_fast() before
reading the pointer to the head of the active list rather than after. [1]
- Add a KASSERT in intr_fast() which asserts that ir_func is non-zero before
calling it. [1]
- Increment interrupt stats after calling the handlers rather than before.
This reduces the delay until direct and fast handlers are serviced, in my
testings by 30% on average for the direct tick interrupt handler, in turn
resulting in less clock drift.
PR: 94778 [1]
Submitted by: Andrew Belashov [1]
MFC after: 2 weeks
|
| |
|
| |
|
| |
|
|
|
|
|
| |
standard syslog port. This allows syslog to easily export lines of interest to
an external logging system.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
with a given module_t. I use this in some the MOD_LOAD event handler for
some test kernel modules to ask the kernel linker to look up the linker
sets in my test modules. (I use linker sets to generate the list of
possible events that I then signal to execute via a sysctl. On non-amd64,
ld(8) would resolve the entire linker set, but on amd64 I have to ask the
kernel linker to do it for me, and having the kernel linker do it works on
all archs.)
|
|
|
|
|
|
|
|
|
|
| |
- Describe msleep() as the primary sleep function now rather than tsleep()
and describe tsleep() and msleep_spin() as variations.
- Try to make the description of msleep() a bit closer to English
(sentences with actual subjects, etc.)
- Document that a priority of 0 now prevents the thread's priority from
being altered.
- Add a history note for wakeup_one().
|