| Age | Commit message (Collapse) | Author |
|---|
|
|
|
level 4 interrupts, just like memory controller bus errors; register the
tcc(4) handler with the right cause register bitmask, and teach imc(4) not
to claim the interrupt if it did not trigger it.
|
|
|
|
|
|
|
|
encoded with shifts. Switch to a file constructed by iterating
through i915_drv.c pciidlist so these will be included.
ok kettenis@
|
|
while here, knock out a section header to avoid a one sentence section;
|
|
requested by mpi@
|
|
reclaiming to the PDU and marker input routines.
m_pullup may return a pointer to the newly allocated mbuf. In this
case m_freem is called by the trunk_input, not by the proto specific
code and pointer to the mbuf is not passed by reference. Therefore
m_freem will either be called on the middle element of the chain
(when the m_pullup call succeeds) or on the stale pointer (when it
frees the chain in the failure case). Fortunately we should never
hit this case as the receive path uniformly uses contiguous chunks
of memory.
Verified with and ok blambert, ok mpi
|
|
|
|
|
|
|
|
|
|
|
|
gpt_chk_hdr() and gpt_chk_parts().
Spotted when investigating zeloff's GPT bug report.
|
|
|
|
|
|
|
|
because that are a union). From Filipe Brandenburger.
|
|
- change output of regress to reflect that
- add test
|
|
- unit tests are functions in main.c
- use test name in output
- add grabbing stdout output of tests
|
|
|
|
a certificate; patch from Meghana Bhat on bz#2436; ok markus@
|
|
|
|
commit 48f8f36a6c8018c2b36ea207aaf68ef5326c5075 on the linux-3.14.y
branch of the linux-stable tree). This brings preliminary support for
the GPU on Intel's Broadwell CPUs. Don't expect these to work
perfectly yet. There are some remaining issues with older hardware as
well, but no significant regressions have been uncovered.
This also updates some of drm core code. The radeondrm code remains
based on Linux 3.8 with some minimal canges to adjust to changes in
the core drm APIs.
Joint effort with jsg@, who did the initial update of the relevant drm
core bits. Committing this early to make sure it gets more testing
and make it possible for others to help getting the remaining wrinkles
straightened out.
|
|
where they end, there is a good chance they are sharing a page with .data,
which obviously needs to remain writable. So only attempt to make them
read-only if we know they have a non-zero size. Original diff from guenther@
based on an earlier diff from me. Fixes ld -Z on alpha.
ok miod@, guenther@
|
|
instead of calling exit(). From Michael Reed.
|
|
|
|
|
|
current ASID value rather than using zero, so that we can avoid writing
back the ASID on exit (and waste cycles because of expensive coprocessor 0
hazards).
While there, use conditional instructions when picking a random TLB set number,
in order to waste one branch prediction cache entry.
|
|
tfp_inval_icache().
|
|
|
|
included at the start of this page;
ok tedu
|
|
Found by Matthew Dillon (Dragonfly). DMA sync hint from tedu@, ok mpi@
|
|
the firmware, rather than zeros. Matches what Linux iwlwifi does.
Spotted by Adrian Chadd (FreeBSD).
ok mpi@
|
|
|
|
ok jmc@, schwarze@
|
|
|
|
This moves around calls to if_ih_insert and if_ih_remove to ensure
that we either have completed port initialization or are going to
tear the port configuration down and don't want any input processes
to get hold of the port.
When trunk_port_destroy is called from the ioctl this would wait for
all input processes to finish and release their references to be able
to disestablish the input handler and ensure full control of the port.
When switching trunkproto it is required for the ioctl context to
be able to touch all trunk ports and the protocol (tr_psc). The
easiest way do this is to disestablish all input handlers (while
making sure they all complete) and then reestablish them after the
trunk reconfiguration is completed.
This avoids getting trunk a separate locking protocol of its own.
ok mpi, suggested by and ok dlg
|
|
|
|
ok dlg, mpi
|
|
iterations and additional locking protection in the future.
Suggested by and ok mpi
|
|
and we want to limit the number of different places where we
access trunk port pointers.
trunk_watchdog should be never called as we don't set up it's
if_timer and trunk_port_watchdog just calls the if_watchdog
from the underlying interface.
It's possible that this is no longer needed due to if_slowtimo/
if_watchdog changes done earlier.
ok mpi
|
|
|
|
|
|
|
|
|
|
specific places.
ok claudio@, benno@
|
|
|
|
|
