Revision 8f4fd86aa5d6aa122619623910065d236592e37c authored by David Woodhouse on 06 January 2021, 15:39:55 UTC, committed by Juergen Gross on 13 January 2021, 15:12:03 UTC
With INTX or GSI delivery, Xen uses the event channel structures of CPU0. If the interrupt gets handled by Linux on a different CPU, then no events are seen as pending. Rather than introducing locking to allow other CPUs to process CPU0's events, just ensure that the PCI interrupts happens only on CPU0. Signed-off-by: David Woodhouse <dwmw@amazon.co.uk> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> Link: https://lore.kernel.org/r/20210106153958.584169-3-dwmw2@infradead.org Signed-off-by: Juergen Gross <jgross@suse.com>
1 parent 3499ba8
| File | Mode | Size |
|---|---|---|
| backlight | ||
| console | ||
| fbdev | ||
| logo | ||
| Kconfig | -rw-r--r-- | 682 bytes |
| Makefile | -rw-r--r-- | 437 bytes |
| display_timing.c | -rw-r--r-- | 512 bytes |
| hdmi.c | -rw-r--r-- | 51.1 KB |
| of_display_timing.c | -rw-r--r-- | 6.6 KB |
| of_videomode.c | -rw-r--r-- | 1.4 KB |
| vgastate.c | -rw-r--r-- | 13.3 KB |
| videomode.c | -rw-r--r-- | 1.1 KB |
Computing file changes ...
