Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| b16b5f31 | 2024-12-03 07:54:20 | Add missing wakeup & cleanup in error path. ok tb@ | ||
| 897b1709 | 2024-12-03 07:51:21 | Use uvm_pagewait() rather than re-rolling it. ok miod@, tb@ | ||
| 7f98e85f | 2024-12-01 10:38:47 | Fix typo in comment | ||
| 8e650cf5 | 2024-12-01 09:05:05 | upd(4): add PercentLoad sensor Reports the % of the available UPS power drawed by output outlets. tested by sthen@, matthieu@ and Walter Alejandro Iglesias ok sthen@ as part of a larger diff | ||
| d223718e | 2024-11-30 17:47:23 | sys/uvideo: add quirk for Jabra PanaCast 20 Jabra PanaCast 20 needs uvideo_vs_negotiation between usbd_set_interface and usbd_open_pipe, otherwise it doesn't work with error: ioctl VIDIOC_DQBUF: Invalid argument OK mglocker@ | ||
| 9497c257 | 2024-11-30 17:43:46 | Regen | ||
| 94ba045d | 2024-11-30 17:41:57 | sys/dev/usb/usbdevs: add Jabra PanaCast 20, to be used in quirks OK mglocker@ | ||
| 5797ad06 | 2024-11-29 06:44:57 | Also call pmap_extract() before entering a page ahead for lower layer faults. As for the upper layer, call pmap_update() only if, at least, a page has been entered. ok tb@, kettenis@ | ||
| a52f395c | 2024-11-29 06:40:57 | When paging ahead, delay calling pmap_extract() after checking for a valid page. While here call pmap_update() only if, at least, a page has been entered. ok tb@, kettenis@ | ||
| d9a6171a | 2024-11-28 18:54:36 | Move cpu_features to hwcap and cpu_features2 to hwcap2 ok jca@ | ||
| db835d32 | 2024-11-28 13:13:03 | Replace magic numbers to macro defined values. Also make it possible to change the amount of 3-port RAM usage by the kernel option. | ||
| 41517b19 | 2024-11-28 02:01:57 | avoid lock contention in __thrsleep and __thrwakeup syscalls turns out the __thrsleep and __thrwakeup syscalls largely coordinate using a single lock per process. if you have heavily threaded code building locks in userland out of thrsleep, this kernel lock gets hammered. this is true even if userland thinks it's operating on separate locks, it all ends up serialised in the kernel. this reduces the throughput of these heavily threaded programs. the big change is hashing thrsleep waiters into an different locks/lists based on their "id" to try and avoid all locks in a process contending on a single lock. the hash is shared by all processes though. the change also avoids having a waiter re-take the lock to avoid contention on the thrwakeup code which is currently holding the lock. __thrsleep and __thrwakeup seem to be largely unused these days, except by go. go still uses it as a backend to it's locks, and also creates a lot of threads which end up contending on the lock. these changes provide an improvement for go programs. the contention was pointed out by nick owens jsing@ and nick owens did a bit of testing | ||
| 14cbb2b5 | 2024-11-27 20:30:15 | In powerpc64 pmap, when replacing a pte, put it in the correct pteg In pte_insert(), if both the primary page table entry group and the secondary pteg are full, then we delete an old pte and replace it with the new pte. We might have set "idx" wrong and inserted the new pte into the wrong pteg (with the wrong PTE_HID bit). This problem almost never happened; it is rare for both ptegs to be full. When the loop "for (try = 0; try < 16; try++)" looks for a slot for the new pte, set "idx" to the new pte's primary pteg. Put it in the primary pteg "idx" or secondary pteg "idx ^ pmap_ptab_mask". When we delete the old pte, set "idx" to the old pte's primary pteg. Eric Gosse reported a bug where the kernel crashed on an unexpected fault. I suspect that a pte fell into the wrong "idx" and got lost. ok kettenis@ | ||
| 0cd9f930 | 2024-11-27 20:11:32 | Change getfp() to return an unBIASed stack pointer; this unbreaks stackdump() which got broken in machdep.c 1.202. It is much simpler to change getfp() than stackdump() which is its only caller. | ||
| 21cb8457 | 2024-11-27 15:23:58 | defer creation of ice(4) ifp until device attachment has succeeded Otherwise we would crash when something goes wrong in ice_attach_hook(). problem found by bluhm@ | ||
| 5e0634cb | 2024-11-27 13:26:42 | Revert "vio: Unlock" This causes some crashes. Revert for now ok sf@ | ||
| 4fda2ec5 | 2024-11-27 12:29:14 | remove unneeded fpu.h include to unbreak the build on archs without it already indirectly included by reg.h on amd64 ok sthen@ | ||
| e4c405f0 | 2024-11-27 11:37:23 | sys/uvideo: add missed abort of transfer pipe in uvideo_vs_close A bulk transfer cannot timeout and must be aborted on close. OK mpi@ | ||
| 8a233859 | 2024-11-27 10:58:07 | Neighbor (fault ahead) pages are never mapped with the wired attribute. Wired faults are always "narrow". That means the fault handler do not try to fault neighbor pages ahead. So do not propagate the `flt->wired' attribute to the corresponding pmap_enter(9) calls and instead assert that it is false whenever neighbor pages are entered in a memory space. ok tb@ | ||
| a8f4448a | 2024-11-27 10:41:38 | Change pgo_get() interface in preparation for running PGO_LOCKED in parallel. - Do not allocate zero-fill'd pages in uao_get(), leave that for PGO_SYNCIO. - Reduce cosmetic differences between uvn_get() and uao_get() ok tb@ | ||
| be8d5ab0 | 2024-11-27 10:33:31 | remove #if 0'd entries for /dev/pcmcia functions removed in 1998 | ||
| 96aab481 | 2024-11-27 10:09:51 | Use uvm_fault_wire() for consistency and to keep VM_FAULT_WIRE usage in uvm/. ok dv@, mlarkin@ | ||
| deef986e | 2024-11-27 05:25:56 | Add ptrace commands used to read/write the XSAVE area of a traced process. Intended to give debuggers access to xmm/ymm registers. Inspired by FreeBSD which exposes a similar set of ptrace commands. ok kettenis@ | ||
| 51248bbd | 2024-11-27 02:40:53 | Enable rx/tx checksum offloading on ivaf(4). from Yuichiro NAITO and jan; test jan ok jan jmatthew | ||
| b5f9b883 | 2024-11-27 02:38:35 | continue enumerating devices if a device is not matched fixes xbf(4) and xnf(4) not attaching on XCP-ng 8.3/Xen 4.17 which has "device/9pfs/" from Joel Knight | ||
| 3aca4c8c | 2024-11-27 02:14:48 | zero attach args; return on missing properties will be removed | ||
| 66cfbb9d | 2024-11-27 01:02:03 | rework rwlocks to reduce pressure on the scheduler and SCHED_LOCK it's become obvious that heavily contended rwlocks put a lot of pressure on the scheduler, and we have enough contended locks that there's a benefit to changing rwlocks to try and mitigate against that pressure. when a thread is waiting on an rwlock, it sets a bit in the rwlock to indicate that when the current owner of the rwlock leaves the critical section, it should wake up the waiting thread to try and take the lock. if there's no waiting thread, the owner can skip the wakeup. the problem is that rwlocks can't tell the difference between one waiting thread and more than one waiting thread. so when the "there's a thread waiting" bit is cleared, all the waiting threads are woken up. one of these woken threads will take ownership of the lock, but also importantly, the other threads will end up setting the "im waiting" bit again, which is necessary for them to be woken up by the 2nd thread that won the race to become the owner of the lock. this is compounded by pending writers and readers waiting on the same wait channel. an rwlock may have one pending writer trying to take the lock, but many readers waiting for it too. it would make sense to wake up only the writer so it can take the lock next, but we end up waking the readers at the same time. the result of this is that contended rwlocks wake up a lot of threads, which puts a lot of pressure on the scheduler. this is noticeable as a lot of contention on the scheduler lock, which is a spinning lock that increases time used by the system. this is a pretty classic thundering herd problem. this change mitigates against these wakeups by adding counters to rwlocks for the number threads waiting to take write and read locks instead of relying on bits. when a thread needs to wait for a rwlock it increments the relevant counter before sleeping. after it is woken up and takes the lock it decrements that counter. this means rwlocks know how many threads are waiting at all times without having to wake everything up to rebuild state every time a thread releases the lock. pending writers and readers also wait on separate wchans. this allows us to prioritise writers and to wake them up one at a time. once there's no pending writers all pending readers can be woken up in one go so they can share the lock as soon as possible. if you are suffering a contended rwlock, this should reduce the amount of time spent spinning on the sched lock, which in turn may also reduce the wall clock time doing that work. the only downside to this change in my opinion is that it grows struct rwlock by 8 bytes. if we can reduce rwlock contention in the future, i reckon i could shrink the rwlock struct again while still avoiding some of the scheduler interactions. work with claudio@ ok claudio@ mpi@ stsp@ testing by many including claudio@ landry@ stsp@ sthen@ phessler@ tb@ and mark patruck | ||
| 7601f687 | 2024-11-26 21:45:35 | enable ice(4) in GENERIC and RAMDISK_CD kernels on amd64 ok deraadt | ||
| 54585ff1 | 2024-11-26 21:21:44 | repair build without ICE_DEBUG set and stop setting it by default | ||
| d8ac2821 | 2024-11-26 17:38:43 | ice(4) contains dlg@ code from ixl(4), add copyright header from there | ||
| 444719c5 | 2024-11-26 17:37:30 | implement ice_txeof(), based on ixl(4) code | ||
| 88d9063a | 2024-11-26 17:36:06 | Enable TSO in ice(4) Tx queue context. Else the device won't send packets. | ||
| ad5417e7 | 2024-11-26 17:34:00 | implement ice_start(), based on code from ixl(4) | ||
| 80e2dad2 | 2024-11-26 17:32:05 | add an rwlock to protect the ice(4) ioctl handler; based on ixl(4) | ||
| c6b373c6 | 2024-11-26 10:42:58 | let bpf pick the first attached dlt when attaching to an interface. this is instead of picking the lowest numbered dlt, which was done to make bpf more predictable with interfaces that attached multiple DLTs. i think the real problem was that bpf would keep the list in the reverse order of attachment and would prefer the last dlt. interfaces that attach multiple DLTs attach ethernet first, which is what you want the majority of the time anyway. but letting bpf pick the first one means drivers can control which dlt they want to default to, regardless of the numeric id behind a dlt. ok claudio@ | ||
| bb6b0345 | 2024-11-26 10:28:27 | Generate a single event when timers advance for more than one tick. Also report the number of events missed due to recursions or skipped ticks to btrace(8). From Christian Ludwig. | ||
| 34e43087 | 2024-11-26 10:10:28 | Make uvmfault_anonget() return errno values instead of converting them. ok miod@, tb@ | ||
| d84bf95d | 2024-11-26 09:51:30 | Remove unused min values and document reserves for pagedaemon & kernel. ok tb@, kn@ | ||
| 44683af5 | 2024-11-25 22:12:18 | Add scmi mailbox transport and perf protocol for cpu frequency management on Snapdragon X Elite. This is not hooked up to cpu/apm yet, so the kernel won't use it to adjust the frequency. Instead the current frequency and power consumption per performance domain are exported as sensors for now. tested by landry@ kettenis@ ok kettenis@ patrick@ | ||
| 399b2cc5 | 2024-11-25 19:30:47 | vio: Unlock, switch to qstart function Run without kernel lock. Use the network stack functions used for multiqueue, but still only run on one queue. Add a virtio interface for an interrupt barrier. ok dlg@ | ||
| 4e1bc1c2 | 2024-11-25 14:39:20 | stop trying to load ice(4) firmware from disk, for now We currently lack the hardware reset code path required for loading firmware. Until this situation changes, stop trying to load firmware from disk. | ||
| 58243cbf | 2024-11-25 13:46:55 | Remove unused `fault_type' argument. | ||
| f3e3a779 | 2024-11-25 13:37:49 | Push the KERNEL_LOCK() down in the aiodone_daemon(). Improve responsiveness during swapping for MP machines without bouncing. When the page daemon is busy writing a lot of clusters without releasing the KERNEL_LOCK() and without allocating. This currently require vm.swapencrypt.enable=0 and a dma_constraint covering the whole address range. Tested by sthen@ and miod@. ok claudio@, tb@ | ||
| 1df50bec | 2024-11-25 13:06:25 | Account for in-flight pages being written to disk when computing page shortage. Due to its asynchronous design, on MP machines, the page daemon was generally over swapping memory resulting in a degenerative behavior when OOM. To prevent swapping more pages than necessary, take the amount of in-flight pages into account when calculating the page shortage. Tested by sthen@ and miod@. ok claudio@, tb@ | ||
| bb43dd77 | 2024-11-25 12:52:11 | remove hw->debug_mask, we are using the ice_debug global variable instead | ||
| 2da9c48e | 2024-11-25 12:51:00 | Do not retry with a single page if paging out a cluster didn't work. Allocations that might fail in uvm_swap_io() are independant from the amount of pages, so retrying with fewer pages is counter productive. Tested by sthen@, ok tb@ | ||
| e151407e | 2024-11-25 12:50:47 | implement ice_config_rss() and its many friends We are not yet enabling RSS since we run in "safe mode", but all this code will be needed when we eventually enable it. Taken from FreeBSD, with tweaks to use our native toeplitz API. | ||
| f9aba9bd | 2024-11-25 12:43:16 | ice(4) rx dma maps don't need to be larger than one mbuf Previous code was needlessly allocating hardmtu-sized dma maps. Each map corresponds to one mbuf, and the device will use up to 5 of them when jumbo frames are received. | ||
| c55453e1 | 2024-11-25 12:35:37 | disable interrupts when taking an ice(4) interface down | ||
| b09e7adf | 2024-11-25 10:40:53 | don't reset the rx queue tail pointer in ice_setup_rx_ctx() We already have mbufs on the ring at this point. Resetting the tail pointer here was causing "no descriptor" errors during Rx. | ||
| e49cad03 | 2024-11-25 04:37:06 | remove EM_NUM, unused and not in SysV ABI documents ok tb@ who tested this with a ports build | ||
| 5cd94c44 | 2024-11-25 00:17:34 | drm/amd/pm: Vangogh: Fix kernel memory out of bounds write From Tvrtko Ursulin f111de0f010308949254ee1cc45df8e6b8e1d7d4 in linux-6.6.y/6.6.63 4aa923a6e6406b43566ef6ac35a3d9a3197fa3e8 in mainline linux | ||
| 20665b8f | 2024-11-25 00:14:52 | drm/amd/display: Adjust VSDB parser for replay feature From Rodrigo Siqueira 0a326fbc8f72a320051f27328d4d4e7abdfe68d7 in linux-6.6.y/6.6.63 16dd2825c23530f2259fc671960a3a65d2af69bd in mainline linux | ||
| 4092cec0 | 2024-11-25 00:12:14 | drm/amd: Fix initialization mistake for NBIO 7.7.0 From Vijendar Mukunda 5e91cd9a34171171c83d462256626c6a8deec2a0 in linux-6.6.y/6.6.63 7013a8268d311fded6c7a6528fc1de82668e75f6 in mainline linux | ||
| 4c69420e | 2024-11-24 22:58:04 | Add support for the "post-power-on-delay-ms" in the MMC power sequencing. From Paul Fertser. | ||
| b3b04c1d | 2024-11-24 22:46:54 | Add RK3399 support. From Paul Fertser. ok dlg@ | ||
| 41b6ab1f | 2024-11-24 22:19:59 | Fix RK3399 USB clock gates. From Paul Fertser. ok dlg@ | ||
| 35bbce86 | 2024-11-24 13:05:14 | Add KASSERT on P_WSLEEP in setrunqueue() and sched_chooseproc(). P_WSLEEP indicates that the thread is still on a CPU executing and has not yet mi_switched away to sleep. So it is a bug to make such a thread runnable or even worse try to switch to it. OK mpi@ | ||
| cf08c0f1 | 2024-11-24 13:02:37 | In setrunnable() also check for P_WSLEEP in the SSTOP case. If a thread is quickly stopped and continued then it is possible that all of this happens between sleep_setup and sleep_finish and so this code needs to check for P_WSLEEP so that a still running thread is put onto the runqueue. OK mpi@ | ||
| d17ca878 | 2024-11-24 12:58:06 | Do not clear P_WSLEEP in ptsigna's SIGCONT handling. cursig() no longer stops threads while called during the sleep transition and so there is no need to clear P_WSLEEP. OK mpi@ | ||
| 32a67d49 | 2024-11-23 21:24:03 | Implement power down if the PMIC is marked as the system power controller in the device tree. From Paul Fertser. | ||
| 1cfc6e0b | 2024-11-22 09:29:41 | Flush the interrupt status register in ahci(4) attach AMD 600 Series AHCI set interrupt bits during sd(4) attaching while using polling mode. Thus, we have to clear them, before enable interrupt handling. Also the AHCI 1.3.1 saids to do this. tested by tobhe@ ok tobhe@, jmatthew@ | ||
| c77b3186 | 2024-11-21 20:15:44 | During IP deliver, propagate correct address family. If ip_deliver() changes the af, e.g. for ip6 over ip4, then it cannot rely on the caller ip_ours() to enqueue the packet in the correct queue. ip_deliver() has to do the enqueue depending on the changed af. from markus@ | ||
| cc51e07c | 2024-11-21 11:58:45 | Let the user provide an alternative perfpolicy when on battery The current behavior of "auto", which implies running at full speed when on AC power, does not fit all the hardware and use cases. For some people it results in more power consumption, more heat, more noise, etc. Extend the semantics of hw.perfpolicy and provide two buttons to specify the desired behavior: sysctl hw.perfpolicy=<policy while on ac>[,<policy while on battery>] Keep the default behavior of "high,auto". People can opt for "auto,auto" or simply "auto" instead. No objection from deraadt@, input and ok sobrado@ sthen@ | ||
| c229d804 | 2024-11-20 22:25:38 | The buffer flipper (incorrectly?) uses pmap_copy_page() from interrupt context (when it calls uvm_pagerealloc_multi()). But the current implementation of pmap_copy_page() assumes it only runs in process context. Use splbio() to block the interrupts while we're doing the copy. Same diff as the one committed to arm64 a bit over a week ago. ok mpi@, jca@ | ||
| e283d8fb | 2024-11-20 13:36:55 | Improve error handling of psp(4) driver. The driver for the AMD platform security processor did use a bunch of EINVAL error codes. It is better to propagate the error up from the subsystem or use more specific values. Rename the variable "ret" to "error" to make clear where we deal with an actual errno(2). Document where and why the error code is ignored. OK hshoexer@ | ||
| 315d09db | 2024-11-20 10:21:22 | No need to call unsleep() if p_wchan is NULL. OK mpi@ | ||
| cd336d15 | 2024-11-20 02:26:53 | use ifq_deq_set_oactive if we're in an if_deq_begin "transaction" reported by and fix tested by afresh@ | ||
| a4f86d2e | 2024-11-20 02:18:45 | provide ifq_deq_set_oactive. ifq_deq_set_oactive is a variation on ifq_set_oactive that can be called inside an if_deq_begin "transaction". afresh@ found de(4) was calling ifq_set_oactive while holding the ifq mutex via ifq_deq_begin, which led to a panic because ifq_set_oactive also tries to take the ifq mutex. ifq_deq_set_oactive assumes the caller is already holding the mutex. de(4) is confusing, so it seemed simpler to add a small tweak to ifqs than try and do major surgery on such a hairy driver. tested by afresh@ | ||
| 1511e544 | 2024-11-19 23:26:35 | use a tailq for the global list of bpf_if structs. this replaces a hand rolled list that's been here since 1.1. ok claudio@ kn@ tb@ | ||
| 6ddbef63 | 2024-11-19 09:41:32 | gather ice(4) hardware counters for debugging | ||
| da9ae00d | 2024-11-19 09:39:57 | implement ice_add_rx_lldp_filter() | ||
| 64a83ff1 | 2024-11-19 06:18:26 | remove forward declaration of struct mount unneeded after uvm_vnp_sync() prototype moved to vnode.h in 2014 | ||
| 83e3fc60 | 2024-11-19 05:49:27 | Teach ddb how to disassemble endbr64. With input on prefix handling and ok jsg@ | ||
| ef4d1ee3 | 2024-11-19 02:31:35 | kill our kids before we die, or there will be panic dlg concurs | ||
| ddee6534 | 2024-11-19 02:11:03 | fix tcpdump on pfsync interfaces. after the last rewrite i was showing bpf ip packets, not the pfsync payload like the PFSYNC DLT expected. this also lets bpf see packets being processed by pfsync input handling, so if you want to see only what's being sent you'll need to filter by direction. reported by Marc Boisis | ||
| 0815c577 | 2024-11-18 08:42:53 | Cast atomic_load_int(9) to signed int when loading `securelevel'. The return value of atomic_load_int(9) is unsigned so needs a cast, otherwise securelevel=-1 gets misrepresented. From Paul Fertser. | ||
| b0d28118 | 2024-11-18 05:32:39 | move bus space extern to bus.h; ok mpi@ | ||
| e8f54a3d | 2024-11-18 02:32:22 | Fix some typos in comments in i386/amd64 bootblocks Also fix some trailing whitespace in comments. From Christian Schulte, thanks | ||
| f7304f60 | 2024-11-18 00:22:24 | drm/amdkfd: Accounting pdd vram_usage for svm From Philip Yang 4c332037fcbb9bb53c46ba4f156951429acc4d97 in linux-6.6.y/6.6.62 68d26c10ef503175df3142db6fcd75dd94860592 in mainline linux | ||
| 2e7772af | 2024-11-17 23:31:01 | bump the "mru" up to MAXMCLBYTES. there's no reason to limit tun/tap to small packets. ok claudio@ | ||
| 05ecc67f | 2024-11-17 23:21:45 | include tun_hdr in the length reported by FIONREAD and kq if it's enabled. | ||
| d97ff3f7 | 2024-11-17 16:35:05 | add qccpucp to GENERIC ok patrick@ | ||
| a921796a | 2024-11-17 12:21:48 | make sure bpfsdetach is holding a bpf_d ref when invalidating stuff. when bpfsdetach is called by an interface being destroyed, it iterates over the bpf descriptors using the interface and calls vdevgone and klist_invalidate against them. however, i'm not sure the reference the interface holds against the bpf_d is accounted for properly, so vdevgone might drop it to 0 and free it, which makes the klist_invalidate a use after free. avoid this by taking a bpf_d ref before calling vdevgone and klist_invalidate so the memory can't be freed out from under the feet of bpfsdetach. Reported-by: syzbot+b3927f8ad162452a2f39@syzkaller.appspotmail.com i wasn't able to reproduce whatever syzkaller did. it's possible this is a double free, but we'll wait and see if it pops up again. ok mpi@ | ||
| 1c386161 | 2024-11-17 00:25:07 | provide network offloads between the kernel and userland again userland can request that network packets that are read from or written to the device special file get prepended with a "tun_hdr" struct. this struct contains bits which say what offloads are requested for the packet, including things like ip/tcp/udp/icmp checksums, tcp segmentation offloads, or ethernet vlan tags. userland can write a packet with any of these offloads requested into the kernel at any time, but has to request which ones it's able to handle coming from the kernel. enabling the tun_hdr struct and which offloads userland can handle is done with a new TUNSCAP ioctl. this is based on the virtio_net_hdr in linux, which jan@ actually implemented and had working with vmd. however, claudio@ and i strongly opposed to what feels like a layer violation by pulling virtio structures into the tun driver, and then trying to emulate virtio/linux semantics in our network stack, and playing catch up when the "upstream" projects decide to change the shape or meaning of these bits. tun_hdr is specific to the openbsd network stack and it's semantics, which simplifies our kernel implementation. jan has been pretty gracious about the extra work on the vmd side of things. tested by and ok jan@ ok claudio@ sthen@ backed this out cos of confusion with the ioctl numbers i picked to controlling this feature. i've picked new numbers that don't conflict this time. | ||
| 03cefa02 | 2024-11-16 21:17:54 | Add qccpucp(4), a driver for the CPUSS Control Processor (CPUCP) mailbox controller. It is used as doorbell for the arm-scmi perf protocol and a prerequisite for cpu frequency management on X Elite chips. ok patrick@ | ||
| 74531700 | 2024-11-16 13:06:06 | Adjust deep logic in cursig() to handle sig_stop specially. If any other signal is pending the stop signal should be deferred. Now cursig() uses ffs() to select the signal and so higher numbered signals like SIGUSR1 would be ignored when going to sleep. So handle default stop signals specially in the deep case, stash them and only use them if no other signal is pending. Fix for signal-stress regress (problem reported by anton@) With and OK mpi@ | ||
| feb640d4 | 2024-11-16 12:54:05 | Remove unreachable check for orphaned process groups in cursig. setsigctx() now does this check and clears sig_stop in that case and instead set sig_ignore. So the check in cursig that is based on sig_stop can never be true. OK mpi@ | ||
| 0aa88a20 | 2024-11-16 10:09:08 | Do not dereference `pve' after releasing `pv_mtx'. Prevent a race where anything can happen on `pve' resultint in an incorrect locking of a given pmap. Found the hardway by sthen@. ok jsg@, miod@, kettenis@, jca@ | ||
| 39788106 | 2024-11-15 15:43:49 | wait for ice(4) software interrupt to occur when flushing queue interrupts This codes runs under IPL_NET. Interrupt processing would get delayed until the ioctl handler was done which is probably not what the device is expecting. | ||
| dc2d0e99 | 2024-11-15 15:42:00 | fix build without ICE_DEBUG | ||
| 4fe5a962 | 2024-11-15 15:41:10 | implement the ice(4) Rx interrupt handler | ||
| 4b15066f | 2024-11-15 15:34:56 | in ice(4), ensure that vsi->max_frame_size gets set dlg@ advised me that our drivers should always configure the largest frame size supported by hardware | ||
| 2e3b1cad | 2024-11-15 04:26:33 | add placeholder for GC 11.5.2 APU | ||
| 90bb45d1 | 2024-11-15 02:59:23 | procmap(8) -> procmap(1); spotted by Avon Robertson | ||
| e0ec580a | 2024-11-15 02:54:01 | sparce -> sparse | ||
| 2c8a74f9 | 2024-11-15 01:22:44 | drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported From Antonio Quartulli a613a392417532ca5aaf3deac6e3277aa7aaef2b in linux-6.6.y/6.6.61 a6dd15981c03f2cdc9a351a278f09b5479d53d2e in mainline linux | ||
| 993abb54 | 2024-11-15 01:19:33 | drm/amdgpu: Fix DPX valid mode check on GC 9.4.3 From Lijo Lazar 3930715c1aefe8e5cbca94144081aa08b466d571 in linux-6.6.y/6.6.61 3ce3f85787352fa48fc02ef6cbd7a5e5aba93347 in mainline linux | ||
| bbaa42a2 | 2024-11-15 01:17:57 | drm/amdgpu: Adjust debugfs register access permissions From Alex Deucher e2574b57990d482cb4310f8d571e728741c711c8 in linux-6.6.y/6.6.61 b46dadf7e3cfe26d0b109c9c3d81b278d6c75361 in mainline linux | ||
| 9eddea1d | 2024-11-15 01:15:31 | drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read() From Alex Deucher 8906728f2fbd6504cb488f4afdd66af28f330a7a in linux-6.6.y/6.6.61 4d75b9468021c73108b4439794d69e892b1d24e3 in mainline linux |