| Age | Commit message (Collapse) | Author |
|---|
|
|
|
ok stsp@
|
|
|
|
|
|
|
|
|
|
ok hackroom
tested by plenty
|
|
ok hackroom
tested by plenty
|
|
LLVM 10 includes a different fix (https://reviews.llvm.org/D71954), so
this change (by kettenis on 2019-02-18) is no longer needed. Thanks to
Brad Smith for providing the removal diff.
ok kettenis@
|
|
The Exar XR17V354 has 4 ports that have a 256-byte FIFO, use a
frequency of 125Mhz, and have a unique sleep register. A custom
interrupt handler is setup in puc for these ports so it can check a
register which reports which ports triggered the interrupt, rather
than having to run comintr for every port every time.
To avoid probing for these ports in com_attach_subr which requires
access to registers that may be reserved on certain platforms, pass
the sc_uarttype from com_puc_attach since the port type is already
known based on the puc device vendor/id.
Input from kettenis, tested in snaps
|
|
confirmed by naddy and deraadt
|
|
|
|
by miod@ where the powerpc64 claimed to be "for all AArch64 platforms".
ok patrick@
|
|
make the three variants more similar and easier to understand. Ensures
consistent error checks and eliminates pointless adapter_buswidth checks when
processing the list of scsi_links.
|
|
ok hackroom
tested by plenty
|
|
|
|
|
|
|
|
|
|
performance at 200 MHz, so restrict the maximum frequency to 150 MHz for now.
This also makes the eMMC on the ODROID-C4 work properly.
|
|
ok patrick@
|
|
on OpenBSD.
ok gkoehler@
|
|
Unused since r1.138 from 2015: "remove cisco hdlc code from sppp(4)".
OK mpi
|
|
Spotted by miod@
|
|
Spotted by miod@
|
|
OK martijn@ mpi@
|
|
let kr_free() do the work. Otherwise a thread currently inside a remote
section could end up not decrementing the number of ongoing sections
while exiting the same remote section.
Reported-by: syzbot+1252e696865efc29b767@syzkaller.appspotmail.com
|
|
packets output out of KERNEL_LOCK. pppx(4) and pipex(4) are ready to
this.
ok yasuoka@ mpi@
|
|
ok patrick@
|
|
and from partial code inspection;
OK dlg@
|
|
SCSI_IS_SCSIBUS_B().
i.e. return true when 'A' is finished probing (sc_child != NULL) and the
sc_link->bus is != sc_child.
|
|
This allows us to use `stackcollapse-bpftrace.pl' from Brendan Gregg's
FrameGraph without pre-processing outputs.
|
|
|
|
|
|
|
|
|
|
Found the hard way by martijn@ on his alpha.
|
|
Needed to build a sparc64 kernel with clang 10.
ok kettenis@
|
|
so that we can reuse them in other compiler_rt routines.
ok kettenis@
|
|
filtering out messages for routes with flags matching any bit in a mask.
This allows routing daemons to opt out of receiving messages for L2 and
broadcast route entries, which they currently discard.
ok dlg@ sthen@ deraadt@
|
|
messages, and save the route flags before deleting the route. For L2
route entries, the RTF_LLINFO flag is cleared during deletion, so saving
the flags beforehand means they're correct in the routing socket message.
ok mpi@
|
|
Reported by Fabian Raetz <fabian.raetz@gmail.com>.
|
|
|
|
setitimer(2) works with timespecs in its critical section. It will be
easier to merge the two critical sections if getitimer(2) also works
with timespecs.
In particular, we currently read the uptime clock *twice* during a
setitimer(2) swap: we call getmicrouptime(9) in sys_getitimer() and
then call getnanouptime(9) in sys_setitimer(). This means that
swapping one timer in for another is not atomic with respect to the
uptime clock. It also means the two operations are working with
different time structures and resolutions, which is potentially
confusing.
If both critical sections work with timespecs we can combine the two
getnanouptime(9) calls into a single call at the start of the combined
critical section in a future patch, making the swap atomic with
respect to the clock.
So, in preparation, move the TIMESPEC_TO_TIMEVAL conversions in
getitimer(2) after the ITIMER_REAL conversion from absolute to
relative time, just before copyout(9). The ITIMER_REAL conversion
must then be done with timespec macros and getnanouptime(9), just like
in setitimer(2).
|
|
If we're replacing the current ITIMER_REAL timer with a new one we
don't need to call timeout_del(9) before calling timeout_add(9).
timeout_add(9) does the work of timeout_del(9) implicitly if the
timeout in question is already pending.
This saves us an extra trip through the timeout_mutex.
|
|
Reuse the kev[] array of sys_kevent() in kqueue_scan() to lower
stack usage.
The code has reset kevp, but not nkev, whenever the retry branch is
taken. However, the resetting is unnecessary because retry should be
taken only if no events have been collected. Make this clearer by
adding KASSERTs.
OK mpi@
|
|
count them because `if_snd' does this.
ok yasuoka@
|
|
Reading the disabled bios on two Dell machines with RV610
passes initial checks but later fails atombios specific checks.
This occurs when running amd64 but not i386.
Returning early when reading the disabled bios will result in calling
radeon_read_platform_bios() and using the bios at 0xc0000 which works
for both systems this was reported for
semarie@ on Dell OptiPlex 755
RV610 0x1002:0x94C3 0x1028:0x0402 0x00
Andy Bradford on Dell DXP051
RV610 0x1002:0x94C1 0x1028:0x0D02 0x00
|
|
From Sam Ravnborg
cea0a7943a30a6d0320c8558a844dd27e8f0aa8b in linux 5.7.y/5.7.15
2a1658bf922ffd9b7907e270a7d9cdc9643fc45d in mainline linux
|
|
|
