From: Avi Kivity <avi@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [RFC][PATCH 0/3]: Fixes to IRQ routing
Date: Wed, 09 Jun 2010 14:02:28 +0300 [thread overview]
Message-ID: <4C0F74C4.90308@redhat.com> (raw)
In-Reply-To: <1276019703-18136-1-git-send-email-clalance@redhat.com>
On 06/08/2010 08:55 PM, Chris Lalancette wrote:
> As we've discussed previously, here is a series of patches to
> fix some of the IRQ routing issues we have in KVM. With this series
> in place I was able to successfully kdump a RHEL-5 64-bit, and RHEL-6
> 32- and 64-bit guest on CPU's other than the BSP. RHEL-5 32-bit kdump still
> does not work; it gets stuck on "Checking 'hlt' instruction". However,
> it does that both before and after this series, so there is something
> else going on there that I still have to debug.
>
> I also need to change the "kvm_migrate_pit_timer" function to migrate the
> timer over to the last CPU that handled the timer interrupt, on the
> theory that that particlar CPU is likely to handle the timer interrupt again
> in the near future.
>
> The other outstanding question about these patches is how to setup the
> workqueue. As it stands I have a single workqueue for all guests. However,
> for efficiency reasons we may want to have one workqueue per guest. Opinions?
>
Perhaps a singlethreaded workqueue per guest? Or perhaps just
schedule_work(), and let the kernel worry about the details?
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-06-09 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 17:55 [RFC][PATCH 0/3]: Fixes to IRQ routing Chris Lalancette
2010-06-08 17:55 ` [RFC][PATCH 1/3] Introduce a workqueue to deliver PIT timer interrupts Chris Lalancette
2010-06-09 2:36 ` Zachary Amsden
2010-06-09 13:23 ` Marcelo Tosatti
2010-06-09 14:16 ` Avi Kivity
2010-06-09 14:40 ` Marcelo Tosatti
2010-06-09 21:17 ` Zachary Amsden
2010-06-10 9:24 ` Avi Kivity
2010-06-10 19:17 ` Zachary Amsden
2010-06-10 16:18 ` Marcelo Tosatti
2010-06-09 10:55 ` Avi Kivity
2010-06-09 13:49 ` Marcelo Tosatti
2010-06-09 14:20 ` Avi Kivity
2010-06-08 17:55 ` [RFC][PATCH 2/3] Allow any LAPIC to accept PIC interrupts Chris Lalancette
2010-06-08 17:55 ` [RFC][PATCH 3/3] In DM_LOWEST, only deliver interrupts to vcpus with enabled LAPIC's Chris Lalancette
2010-06-09 11:01 ` Gleb Natapov
2010-06-09 11:08 ` Avi Kivity
2010-06-09 11:20 ` Gleb Natapov
2010-06-09 11:22 ` Avi Kivity
2010-06-09 11:02 ` Avi Kivity [this message]
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=4C0F74C4.90308@redhat.com \
--to=avi@redhat.com \
--cc=clalance@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.