search for: genirq

This is a note to let you know that I''ve just added the patch titled genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier to the 3.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: genirq-add-irqf_resume_early-and-resume-such-irqs-earlier.patch and it can be fo...

On Mon, Dec 19, 2022 at 05:36:02PM +0800, Yongji Xie wrote: > On Mon, Dec 19, 2022 at 3:33 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Mon, Dec 05, 2022 at 04:41:17PM +0800, Xie Yongji wrote: > > > Export irq_create_affinity_masks() so that some modules > > > can make use of it to implement interrupt affinity > > > spreading

Ingo Molnar wrote: > * Ingo Molnar <mingo@elte.hu> wrote: > > >> no, that's not the case: next_timer_interrupt() is the NO_IDLE_HZ >> method of doing things - while in the NO_HZ case you are supposed to >> use clockevent devices to program timer hardware. >> We don't have a clockevent device. But we need NO_IDLE_HZ support, which NO_HZ

Ingo Molnar wrote: > * Ingo Molnar <mingo@elte.hu> wrote: > > >> no, that's not the case: next_timer_interrupt() is the NO_IDLE_HZ >> method of doing things - while in the NO_HZ case you are supposed to >> use clockevent devices to program timer hardware. >> We don't have a clockevent device. But we need NO_IDLE_HZ support, which NO_HZ

...=pci.0,addr=0x7: Device initialization failed. qemu-system-x86_64: -device vfio-pci,host=03:01.0,id=hostdev1,bus=pci.0,addr=0x7: Device 'vfio-pci' could not be initialized 2014-03-12 16:48:48.639+0000: shutting down --><-- /var/log/syslog Mar 12 18:07:45 father kernel: [34317.290958] genirq: Flags mismatch irq 16. 00000000 (vfio-intx(0000:03:01.0)) vs. 00000080 (ehci_hcd:usb1) --><-- as i have only 2 pci slots on the board and no other board with serious VT-d/IOMMU support i have no way to swap slots. as the second card shared IRQ 16 with the ehci controller i soft-removed the...

irq: Exclude percpu IRQs from being fixed up Xen spin unlock uses spurious ipi "lock_kicker_irq" to wake up blocked vCPUs waiting on that lock. This irq should always be disabled. However, when Dom0 is shuting down, function fixup_irqs is called which unmasks all irqs. Function unmask_irq effectively re-enables lock_kicker_irq and its irq handler is invoked which reports bug and crashes

https://bugs.freedesktop.org/show_bug.cgi?id=105319 Bug ID: 105319 Summary: DRM: EVO timeout with kernel 4.15.x Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau