| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in vn_rdwr_inchunks(), allowing other processes to gain an exclusive
lock on the vnode. Specifically: directory scanning, to avoid a race to the
root directory, and multiple child processes coring simultaniously so they
can figure out that some other core'ing child has an exclusive adv lock and
just exit instead.
This completely fixes performance problems when large programs core. You
can have hundreds of copies (forked children) of the same binary core all
at once and not notice.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
We still have to account for a copyin. Make sure the copyin will
succeed by passing the FreeBSD syscall a pointer to userspace,
albeit one that's automagically mapped into kernel space.
Reported by: mr, Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
Tested by: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
|
|
|
|
|
|
|
| |
with softupdates dangling deps.
Submitted by: peter
MFC: ASAP :)
|
|
|
|
|
|
|
|
| |
with weird PCI-PCI bridge configurations to work. Defining
PCI_ALLOW_UNSUPPORTED_IO_RANGE causes the sanity checks to pass even
with out of range values.
Reviewed by: msmith
|
| |
|
| |
|
| |
|
|
|
|
| |
proper value.
|
| |
|
|
|
|
|
|
|
| |
for securelevel_ge() and securelevel_gt(), I was a little surprised,
but fixed it. Turns out that it was the code that was inverted, during
a whitespace cleanup in my commit tree. This commit inverts the
checks, and restores the comment.
|
|
|
|
| |
of minor problems and remove some debugging code.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixed the problem on the 3 platforms I've been able to test on.
I'm still of the oppinion that the BIOS should take care of this,
however some board makers only apply this when they spot a
SBLive! soundcard, but the problem exists even without a SBLive!.
This fix should probably go somewhere else, but for now I'll
keep it here since we havn't got a central place to put
such things.
|
|
|
|
|
|
|
| |
problems currently experienced in -CURRENT.
This should fix the problem that the PS/2 mouse is detected
twice if the acpi module is not loaded on some systems.
|
|
|
|
| |
and BCM5401 PHYs.
|
|
|
|
|
| |
whatever mega-commit. This goes some way towards adding support for
writeable files (needed by procfs).
|
|
|
|
|
| |
whatever mega-commit. No real functional changes, just some experiments /
work in progress.
|
|
|
|
|
|
|
|
| |
refering to securelevels; also, update the unprivileged process text
to better indicate the scope of actions permittable when any system
flags are already set (limited).
Submitted by: Udo Schweigert <udo.schweigert@siemens.com>
|
|
|
|
|
|
|
|
| |
so convert those characters to octal notation. Also convert
backslashes to octal notation to avoid confusion.
Reviewed by: des
MFC after: 1 week
|
|
|
|
|
| |
processes and the actual securelevel check: make the comment use '> 0'
instead of inverted '<= 0'.
|
| |
|
|
|
|
|
|
|
| |
to try and extract node attributes from an RPC reply even if none
were present.
Reviewed by: peter
|
| |
|
|
|
|
| |
addresses greater than 256M (the page size for region 6 and 7).
|
|
|
|
| |
in SKI.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
it to call ExitBootServices.
|
|
|
|
|
| |
we start changing translation registers. Also, call ExitBootServices
before we jump into the kernel.
|
| |
|
|
|
|
| |
the loader.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sizeof(struct inode) into a new malloc bucket on the i386. This
didn't happen in -current due to the removal of i_lock, but it does
no harm to apply the workaround to -current first.
Reduce the size of the i_spare[] array in struct inode from 4 to
3 entries, and change ext2fs to use i_din.di_spare[1] so that it
does not need i_spare[3].
Reviewed by: bde
MFC after: 3 days
|
| |
|
|
|
|
| |
calling various firmware functions.
|
|
|
|
| |
- Cosmetic change
|
|
|
|
|
|
| |
remove a useless assignment and move a comment.
Submitted by: Thomas Moestl
|
|
|
|
| |
+ Document our -CURRENT debugging bits
|
| |
|
|
|
|
|
|
|
|
|
| |
we're at least consistent with what tcsendbreak(3) is documented
to do.
MFC after: 2 weeks
Note, the MFC will be to sys/dev/dgb/dgm.c on the RELENG_4 branch
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
I am not sure if this is absolutely necessary on all systems. Yet,
there certainly are motherboards and notebook systems which require
this, although there are other systems which just don't. I hope we
shall know when to do this on which systems, as the development of our
ACPI subsystem progresses... (I know we didn't need this for the APM
resume.)
|
|
|
|
| |
Pointy-hat to: peter
|
|
|
|
|
|
| |
rxcsum capabilities.
Reviewed by: wpaul
|
|
|
|
|
|
|
|
| |
all the debugging code into the function versions of the mutex operations
in kern_mutex.c. This reduced the __mtx_* macros to simply wrappers of
the _{get,rel}_lock_* macros, so the __mtx_* macros were also abolished in
favor of just calling the _{get,rel}_lock_* macros. The tangled hairy mass
of macros calling macros is at least a bit more sane now.
|