| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
we loop through all the list of NICs (struct ifnet), holding the lock on
it and then do a name lookup with ifunit() whilst holding it.
|
|
|
|
| |
an explicit bcopy() -- it probably does a better job.
|
|
|
|
|
|
|
| |
device.
Submitted by: Martin Nilsson <martin@gneto.com>
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to: Charles Smeijer for getting me my AS600.
|
|
|
|
|
|
|
|
|
| |
descriptions of items from each other and have related things appear
in the same nesting 'level'.
The .Fn function/macro, and bump document date.
Reviewed by: jkoshy
|
|
|
|
|
|
| |
Remove outdated info on install media.
Submitted by: "William H. Magill" <magill@mcgillsociety.org>
|
|
|
|
|
| |
PR: kern/75923
Submitted by: Matthew D. Fuller <fullermd@over-yonder.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Fix the MP Table pci bridge drivers to not probe the configuration table
unless we actually have one. Machines using a default configuration do
not have such a table.
- Only allow default configuration types of 5 (ISA + PCI) and 6 (EISA +
PCI) as the others are not likely to work. Types 1 through 4 use an
external APIC (probably with 80486 processors) which we certainly do not
support, and type 7 uses an MCA bus which has not been tested with the
new MP Table code.
- Correct the fact that the single I/O APIC in a default configuration has
an ID of 2, not 0.
- Fix off by one errors in setting the bus types from the default_data[]
arrays for default configurations.
- Explicitly configure each of the 16 interrupt pins on the sole I/O APIC
when using a default configuration. This is especially helpful for type
6 (EISA + PCI) since the EISA interrupts need to have their polarity
programmed based on the values in the ELCR.
Much thanks to the submitter and tester who endured several rounds of
testing to get this fixed.
MFC after: 1 week
Tested by: Georg Schwarz georg dot schwarz at freenet dot de
|
| |
|
|
|
|
|
|
|
| |
Make sure we don't confuse the reader by claiming it is.
PR: docs/75615
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
|
| |
|
|
|
|
| |
argument description list.
|
|
|
|
|
|
| |
- List of struct statfs fields that are related to file systems, much
like the list in stat.2 for the userlevel `struct stat'.
- Bump document date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
complementing the existing special case of a not existing /dev prefix
with the recognition of an already existing /dev prefix.
This implicitly solves the following two issues related to working on
GEOM devices /dev/foo/bar (which have the GEOM provider name "foo/bar")
with the expected commands like "bsdlabel /dev/foo/bar":
1. the error "Geom not found" when trying to write or edit the BSD
label (because previously the incorrect GEOM name "bar" instead of
"foo/bar" was derived from "/dev/foo/bar").
2. the multiple times reported "magically introduced" partition offset
of 63 blocks and the resulting errors like "partition extends past
end of unit" and "partition c doesn't start at 0!".
This implicitly resulted because bsdlabel(8) determines the "MBR
offset" via GEOM and (intentionally) silently falls back to an offset
of 0 if it could not be queried (which is the case if the name was
incorrectly derived).
Usually (at least on PCs) the offset for the first slice is 63 blocks
and bsdlabel(8) automatically subtracts them from the absolute
offsets in the read on-disk BSD label, resulting in the display of an
effective offset of 0. If the GEOM query fails, the assumed offset of
0 is subtracted and an incorrect effective offset of 63 is displayed
and tried to be worked upon.
Reviewed by: pjd
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
- Apply __unused on unused parameters
- Use const where suitable
- Use PRIu64 instead of the deprecated %q
- Bump WARNS to 6
|
| |
|
| |
|
|
|
|
|
|
| |
list for the valid flag values. This way, if VFS_UNMOUNT(9) supports
more flags in the future, adding a single list item is going to be
easy and all the flags are going to be in one place.
|
| |
|
|
|
|
| |
Approved by: phk
|
|
|
|
|
|
| |
(since revision 1.173 of src/sys/sys/mount.h).
Update its prototype, the argument list description and bump the date.
|
|
|
|
|
| |
Submitted by: Hideyuki KURASHINA <rushani@FreeBSD.org>
MFC after: 1 week
|
|
|
|
|
|
| |
macro arguments expected by SYSCALL_MODULE().
MFC after: 3 days
|
|
|
|
| |
Noticed by: krion
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
note that these versions numbers refer to moddepend, not the current
module.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
cuts to the chase and fills in a provided s/g list. This is meant to optimize
out the cost of the callback since the callback doesn't serve much purpose for
mbufs since mbuf loads will never be deferred. This is just for amd64 and
i386 at the moment, other arches will be coming shortly.
|
| |
|
|
|
|
|
| |
Submitted by: Peter Jeremy <PeterJeremy@optushome.com.au>
MFC after: 5 days
|
|
|
|
|
| |
PERC 3 controllers. This is needed to keep the PM code from powering them
down.
|
|
|
|
|
|
|
|
|
|
|
| |
queue and (possibly) unlocking the containing object from
vm_page_alloc() to vm_page_select_cache(). Recent optimizations to
vm_map_pmap_enter() (see vm_map.c revisions 1.362 and 1.363) and
pmap_enter_quick() have resulted in panic()s because vm_page_alloc()
mistakenly unlocked objects that had not been locked by
vm_page_select_cache().
Reported by: Peter Holm and Kris Kennaway
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
the first column is performed using /**, not /*-.
|
|
|
|
|
|
|
| |
held. (It causes a "sleeping without a mutex" assertion failure in
msleep.)
MFC after: 3 days
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
magic.
|
| |
|
|
|
|
|
|
| |
from 4.x kernel config files. User's wishing to upgrade from 4.x to 6
will need to go through 5.x, or grab this script from there. These
scripts will remain in RELENG_5...
|
| |
|
| |
|