From: Jan Kiszka <jan.kiszka@siemens.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH v3 1/3] Introduce a workqueue to deliver PIT timer interrupts.
Date: Mon, 16 Apr 2012 18:33:26 +0200 [thread overview]
Message-ID: <4F8C49D6.9010603@siemens.com> (raw)
In-Reply-To: <1276722673-19011-2-git-send-email-clalance@redhat.com>
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
next prev parent reply other threads:[~2012-04-16 16:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 21:11 [PATCH v3 0/3]: Fixes to IRQ routing Chris Lalancette
2010-06-16 21:11 ` [PATCH v3 1/3] Introduce a workqueue to deliver PIT timer interrupts Chris Lalancette
2012-04-16 16:33 ` Jan Kiszka [this message]
2012-04-16 17:07 ` Avi Kivity
2012-04-17 9:31 ` Gleb Natapov
2012-04-17 10:23 ` Avi Kivity
2012-04-17 10:26 ` Gleb Natapov
2012-04-17 10:29 ` Avi Kivity
2012-04-17 10:31 ` Gleb Natapov
2012-04-17 10:42 ` Avi Kivity
2012-04-17 10:43 ` Avi Kivity
2012-04-17 11:05 ` Gleb Natapov
2012-04-17 12:00 ` Avi Kivity
2012-04-17 12:03 ` Gleb Natapov
2012-04-17 12:06 ` Avi Kivity
2012-04-17 16:15 ` Jan Kiszka
2012-04-17 16:17 ` Avi Kivity
2012-04-18 8:04 ` Gleb Natapov
2012-04-18 8:25 ` Avi Kivity
2012-04-18 8:27 ` Gleb Natapov
2010-06-16 21:11 ` [PATCH v3 2/3] Allow any LAPIC to accept PIC interrupts Chris Lalancette
2010-06-16 21:11 ` [PATCH v3 3/3] In DM_LOWEST, only deliver interrupts to vcpus with enabled LAPIC's Chris Lalancette
2010-06-18 17:44 ` [PATCH v3 0/3]: Fixes to IRQ routing Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F8C49D6.9010603@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox