- Subject: Re: [PATCH v3 1/3] Introduce a workqueue to deliver PIT timer interrupts.
- From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
- Date: Mon, 16 Apr 2012 18:33:26 +0200
- Cc: kvm@xxxxxxxxxxxxxxx, Marcelo Tosatti <mtosatti@xxxxxxxxxx>, Avi Kivity <avi@xxxxxxxxxx>, Gleb Natapov <gleb@xxxxxxxxxx>
- In-reply-to: <1276722673-19011-2-git-send-email-clalance@redhat.com>
- References: <1276722673-19011-1-git-send-email-clalance@redhat.com> <1276722673-19011-2-git-send-email-clalance@redhat.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
On 2010-06-16 23:11, Chris Lalancette wrote:
> We really want to "kvm_set_irq" during the hrtimer callback,
> but that is risky because that is during interrupt context.
> Instead, offload the work to a workqueue, which is a bit safer
> and should provide most of the same functionality.
Unfortunately, workqueues do not have fixed kthread associations (and
"kvm-pit-wq" would be too unspecific when running multiple VMs). So I
just realized that this subtly breaks the ability to run KVM guests with
RT priority (boot managers with timeouts hang as the workqueue starves).
Before throwing some kthread_worker at this, could someone help me
recalling what was "risky" here? That the PIT IRQ may have to be
broadcast to a large number of VCPUs? I would offer to include this
information in my changelog. ;)
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Linux Kernel]
[Linux SCSI]
[XFree86]