From: Gleb Natapov <gleb@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/3]: Fixes to IRQ routing
Date: Mon, 14 Jun 2010 14:21:40 +0300 [thread overview]
Message-ID: <20100614112140.GF21797@redhat.com> (raw)
In-Reply-To: <1276202647-1598-1-git-send-email-clalance@redhat.com>
On Thu, Jun 10, 2010 at 04:44:04PM -0400, 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.
>
> Changes since RFC:
> - Changed ps->inject_lock from raw_spinlock_t to spinlock_t
> - Fixed up some formatting issues
> - Changed to have one PIT workqueue per-guest
> - Remember to cancel_work_sync when destroying the PIT
>
> Chris Lalancette
>
Looks good to me.
--
Gleb.
prev parent reply other threads:[~2010-06-14 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 20:44 [PATCH 0/3]: Fixes to IRQ routing Chris Lalancette
2010-06-10 20:44 ` [PATCH 1/3] Introduce a workqueue to deliver PIT timer interrupts Chris Lalancette
2010-06-11 17:35 ` Marcelo Tosatti
2010-06-12 4:15 ` Yang, Sheng
2010-06-12 5:18 ` Zachary Amsden
2010-06-10 20:44 ` [PATCH 2/3] Allow any LAPIC to accept PIC interrupts Chris Lalancette
2010-06-10 20:44 ` [PATCH 3/3] In DM_LOWEST, only deliver interrupts to vcpus with enabled LAPIC's Chris Lalancette
2010-06-14 11:21 ` Gleb Natapov [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=20100614112140.GF21797@redhat.com \
--to=gleb@redhat.com \
--cc=clalance@redhat.com \
--cc=kvm@vger.kernel.org \
/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