RFC run hpet on a dedicated thread
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | irq: introduce route method in IRQState to get gsihw/ include/ | +44 | 0 replies | |
| 2/5 | irq: implement route method of ioapichw/ hw/ hw/ +3 more | +40 | 0 replies | |
| 3/5 | irqfd: equip irqfd with polarityhw/ hw/ include/ +2 more | +16 | 0 replies | |
| 4/5 | hpet: deliver irq by irqfd when in dedicated thread modehw/ | +50 | 0 replies | |
| 5/5 | hpet: run on dedicate threadhw/ | +30 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Qemu-devel] [RFC 0/5] run hpet on a dedicated thread
Nowadays, we run hpet on iothread. But there are so many undetermined jobs on iothread. It will heavily affect the accuracy of hpet's timing. When running on a dedicated thread, the accuracy of timing is only determined by scheduler. which is more fixed.
This series depend on the thread-safe patches for timers. And it is just for discussion. And code is premature.
Liu Ping Fan (5):
irq: introduce route method in IRQState to get gsi
irq: implement route method of ioapic
irqfd: equip irqfd with polarity
hpet: deliver irq by irqfd when in dedicated thread mode
hpet: run on dedicate thread
hw/core/irq.c | 39 ++++++++++++++++++++++ hw/core/qdev.c | 8 +++++ hw/i386/kvm/i8259.c | 8 ++++- hw/i386/kvm/ioapic.c | 21 +++++++++++- hw/i386/pc_q35.c | 4 +-- hw/misc/vfio.c | 4 +-- hw/timer/hpet.c | 85 ++++++++++++++++++++++++++++++++++++++++++++--- hw/virtio/virtio-pci.c | 2 +- include/hw/irq.h | 5 +++ include/hw/qdev-core.h | 2 ++ include/sysemu/kvm.h | 4 ++- kvm-all.c | 14 ++++---- linux-headers/linux/kvm.h | 3 ++ 13 files changed, 180 insertions(+), 19 deletions(-)
Signature · 1 line
1.8.1.4