| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This gives +10% performance on simple tests, so definitly worth it.
A few percent more could be had by not using M_ZERO'd alloc's, but
we then need to clear fields all over the place to be safe, and
that was deemed not worth the trouble (and it makes life dangerous).
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
be sure to increment the refcount of the argument so it is not
prematurely deleted. This is a workaround and may appear in a different
form in ACPI-CA. This fixes battery evaluation on Thinkpads that was
broken by fixing the Dell battery state.
Submitted by: Luming Yu <luming.yu@intel.com>
|
| |
| |
| |
| | |
less) latest from QLogic.
|
| | |
|
| | |
|
| |
| |
| |
| | |
failed to notice that it's #if 0'ed out.
|
| |
| |
| |
| |
| |
| |
| |
| | |
of the functions in libkern. Without this, parts of the kernel would
reference a non-existent (undeclared and undefined) ffs() function; the
only reason this didn't break the kernel build is that gcc happens to
have a built-in ffs() and incorrectly fails to warn about the lack of
prototypes for built-in functions.
|
| | |
|
| | |
|
| |
| |
| |
| | |
contigmalloc() instead of calling bzero().
|
| |
| |
| |
| |
| |
| |
| | |
http://sources.zabbadoz.net/freebsd/patchset/110-ipsec-netkey-key.diff
Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
Reviewed by: itojun
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
http://sources.zabbadoz.net/freebsd/patchset/110-ipsec-netkey-key.diff
with some modification.
Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
Reviewed by: itojun
Obtained from: KAME
|
| |
| |
| |
| | |
ndis_cpu_cnt().
|
| | |
|
| |
| |
| |
| |
| | |
and receive FCS-less RFC1490-"bridged" Ethernet packets that are
currently just ignored.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ithread_remove_handler() may fail to remove the interrupt handler if
it decides to let the ithread do the removal. The problem is that during
boot "cold" is set, which causes msleep() to return immediately. This
will cause ithread_remove_handler() to fail to wait for the ithread
to do the removal from the handler TAILQ before freeing the handler
back to the heap. Bad things will happen when some other user of the
TAILQ, such as ithread_add_handler() or the actual ithread attempts to use
the freed handler. Fix the problem by forcing ithread_remove_handler()
to do the actual removal itself if the "cold" flag is set.
Reviewed by: jhb
|
| |
| |
| |
| | |
Centralize the definition to make it easier to change.
|
| |
| |
| |
| |
| | |
Tested on: AMD64
Reviewed by: wpaul
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Submitted by: Sean Welch <welchsm@earthlink.net>
MFC after: 1 week
|
| |
| |
| |
| | |
both master and slave at the same time confusing the probe code.
|
| |
| |
| |
| | |
acpi_toshiba(4) driver with ACPI_DEBUG and thus fix LINT on i386.
|
| |
| |
| |
| |
| |
| |
| |
| | |
kmem_free(). Note: The FreeBSD-specific code in this file has been
subsumed by the FreeBSD-specific header file, pdq_freebsd.h. That header
file already specifies the use of contigmalloc() and contigfree(). Thus,
the purpose of this change is to avoid having nonsensical examples of
FreeBSD-specific memory allocation in our source tree.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
nexus code no longer searches for interrupt controllers.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the MacIO chip and PSIM's IOBus. Bus-specific drivers should
use the identify method to attach themselves to nexus so
interrupt can be allocated before the h/w is probed. The
'early attach' routine in openpic is used for this stage
of boot. When h/w is probed, the openpic can be attached
properly. It will enable interrupts allocated prior to
this.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and add_child entry point to allow devices to use the identify
method to add themselves if need be (e.g. openpic, syscons).
Export interrupt-controller-add routine for extern int cntlr drivers.
Eliminate recursive OFW device-tree walk and only iterate the
top-level ala sparc64. Allow child devices to set the device
type with write_ivars.
Step 1 of many in removing the hard-dependency on OpenFirmware.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Obtained from: KAME
|
| |
| |
| |
| |
| | |
Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
Reviewed by: itojun
|
| |
| |
| |
| | |
us closer to being able to run the Intel PRO/Wireless 5000 driver.
|
| |
| |
| |
| |
| | |
vm_page_alloc_contig() will be removed after the three remaining drivers
that use it are also converted to contigmalloc().
|
| |
| |
| |
| | |
Note that the min is actually constrained to IF_MINMTU by the if layer.
|
| |
| |
| |
| |
| | |
Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
Reviewed by: itojun
|
| |
| |
| |
| |
| | |
Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
Reviewed by: itojun
|
| |
| |
| |
| |
| |
| |
| |
| | |
map ranges that are smaller than what our resource manager code knows
is available, rather than requiring that they match exactly. This
fixes a problem with the Intel PRO/1000 gigE driver: it wants to map
a range of 32 I/O ports, even though some chips appear set up to
decode a range of 64. With this fix, it loads and runs correctly.
|