| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
than our other platforms.
|
|
|
|
| |
<sys/file.h>.
|
|
|
|
| |
<sys/file.h> or <sys/socketvar.h>.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
modules (ie. procfs.ko).
When the kernel loads dynamic filesystem module, it looks for any of the
VOP operations specified by the new filesystem that have not been registered
already by the currently known filesystems. If any of such operations exist,
vfs_add_vnops function calls vfs_opv_recalc function, which rebuilds vop_t
vectors for each filesystem and sets all global pointers like ufs_vnops_p,
devfs_specop_p, etc to the new values and then frees the old pointers. This
behavior is bad because there might be already active vnodes whose v_op fields
will be left pointing to the random garbage, leading to inevitable crash soon.
Submitted by: Alexander Kabaev <ak03@gte.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
kern_linker.c and rev. 1.237 of vfs_syscalls.c since these are not the
source of the recent panics occuring around kldloading file system
support modules.
Requested by: rwatson
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
{esp6, ah6}_ctlinput. Previous ones were uninitialized
auto variables, which were completely bogus.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
| |
duplicate include.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Pointy hat to: tmm
|
|
|
|
|
| |
I have no idea why the original committer even used it (in its KERNFORMAT
spelling) as there is no a.out version.
|
|
|
|
| |
Pointy hat to: amorita
|
|
|
|
|
| |
to increase the lenght of the command line if needed. The setting of FMT
also gets in the cross bootstrapping way for new platforms.
|
|
|
|
| |
To commit it for real.
|
|
|
|
|
| |
to remember. Nobody in the right sense of their mind would run IP on
the parallel port on Alpha so comment this one out.
|
|
|
|
|
|
| |
architecture labels as well.
Sponsored by: DARPA, NAI Labs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The conclusion is that this method really can tell the perfect from the
less than perfect ACPI counters.
It is in fact probably a bit more discriminative than that, but we
will rather condemn some otherwise perfect counters to the slightly
slower "-safe" version, than certify a counter as perfect which
will let us down later.
Many thanks to all the people who sent email reports!
|
| |
|
|
|
|
|
|
|
|
|
| |
agnostic way.
Collapse the MBR and MBREXT methods into one file and make them endian/width
agnostic.
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
|
|
|
| |
where a sysctl within 20 seconds of a cache_drain could yield negative "USED"
counts.
Also, grab the uma_mtx while in the sysctl handler. This hadn't caused
problems yet because Giant is held all the time.
Reported by: kkenn
|
|
|
|
| |
that point.
|
|
|
|
|
| |
were not outdented to preserve non-KNF lining up of code with parentheses.
Switch to KNF formatting.
|
|
|
|
|
|
| |
not removing tabs before "__P((", and not outdenting continuation lines
to preserve non-KNF lining up of code with parentheses. Switch to KNF
formatting and/or rewrap the whole prototype in some cases.
|
|
|
|
|
|
| |
not removing tabs before "__P((", and not outdenting continuation lines
to preserve non-KNF lining up of code with parentheses. Switch to KNF
formatting and/or rewrap the whole prototype in some cases.
|
|
|
|
|
| |
were not outdented to preserve non-KNF lining up of code with parentheses.
Switch to KNF formatting in some cases.
|
|
|
|
|
| |
were not outdented to preserve non-KNF lining up of code with parentheses.
Switch to KNF formatting.
|
|
|
|
| |
were not removed.
|
|
|
|
|
|
|
|
|
|
|
| |
[1] Support the Sony VAIO Jogdial in moused(8).
[2] Modify spic(4) to support additional Sony VAIO models.
Submitted by: [1] Juriy Goloveshkin <j@gu.ru>,
[2] Akira Funahashi <funa@funa.org>
Tested by: cjh, jim, Jerry A! <jerry@thehutt.org>
Approved by: nsayer
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
- change the IOMMU support code so that it supports overcommittting the
available DVMA memory, while still allocating as lazily as possible.
This is achieved by limiting the preallocation, and deferring the
allocation to map load time when it fails. In the latter case, the
DVMA memory reserved for unloaded maps can be stolen to free up enough
memory for loading a map.
- allow NULL settings in the method tables, and search the parent tags
until an appropriate implementation is found. This allows to remove some
kluges in the old implementation.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the bus-dependent code and to be able to support more systems. The core
of the new code is mostly obtained from NetBSD.
Kluge the interrupt routing methods of the psycho and apb drivers so
that an intline of 0 can be handled for now; real routing is still not
possible (all intline registers are preinitialized instead); this will
require a sparc64-specific adaption of the driver for generic PCI-PCI
bridges with a custom routing method to work right.
|
|
|
|
| |
KVA upon activation so that rman_get_virtual() works as expected.
|
|
|
|
|
|
| |
serial number probing.
MFC after: 1 week
|
|
|
|
|
| |
caused by IOMMU misses to aid debugging. This will only work on
UltraSPARC-IIi and IIe.
|