All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Lalancette <clalance@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 5/5] Fix kdump under KVM.
Date: Wed, 28 Oct 2009 11:21:42 +0100	[thread overview]
Message-ID: <4AE81B36.5010104@redhat.com> (raw)
In-Reply-To: <20091027174246.GA10473@amt.cnet>

Marcelo Tosatti wrote:
> On Tue, Oct 27, 2009 at 05:41:07PM +0100, Chris Lalancette wrote:
>> This patch is the main point of the series.  In order for
>> kdump to properly work inside a KVM guest, we need to make
>> sure that all VCPUs in virtual wire APIC mode get kicked
>> to try and pick up the timer interrupts.  To do this,
>> we iterate over the CPUs and deliver interrupts to the
>> proper VCPUs.
>>
>> I don't love the concept of doing kvm_irq_kick_vcpus() from
>> within pit_timer_fn().  A PIT is not connected to a CPU at all,
>> only to a PIC or APIC.  However, if a CPU enters idle, this is
>> the only way to wake it up to check for the interrupt.
> 
> The reason the PIT interrupt was fixed to BSP is:
> 
> http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg13250.html
> 
> Perhaps enhancing ioapic_deliver's (irq == 0) check to bypass the       
> destination overwrite in case its programmed by the guest to 
> a single CPU would fix it?

Ug, nasty.  I definitely don't want to re-introduce that bug.  What exactly do
you mean by "fix it"?  Do you mean fix the original RHEL-5.1 PAE issue, or fix
the kdump issue?

-- 
Chris Lalancette

  reply	other threads:[~2009-10-28 10:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 16:41 [PATCH 0/5]: Fix kdump under KVM Chris Lalancette
2009-10-27 16:41 ` [PATCH 1/5] Fix up some comments around the source tree Chris Lalancette
2009-10-27 16:41 ` [PATCH 2/5] Remove KVM_REQ_PENDING_TIMER Chris Lalancette
2009-10-27 16:41 ` [PATCH 3/5] Remove references to VCPU in i8254 Chris Lalancette
2009-10-27 16:41 ` [PATCH 4/5] Remove timer.c Chris Lalancette
2009-10-27 16:41 ` [PATCH 5/5] Fix kdump under KVM Chris Lalancette
2009-10-27 17:42   ` Marcelo Tosatti
2009-10-28 10:21     ` Chris Lalancette [this message]
2009-10-28 12:41       ` Marcelo Tosatti
2009-10-30 12:23         ` Chris Lalancette
2009-10-30 13:07           ` Marcelo Tosatti
2009-10-30 15:28             ` Chris Lalancette
2009-10-30 18:03               ` David S. Ahern
2009-10-30 22:21                 ` Marcelo Tosatti
2009-10-30 22:19               ` Marcelo Tosatti
2009-11-01 15:21           ` Avi Kivity
2009-11-02 13:22             ` Chris Lalancette
2009-11-02 13:30               ` Avi Kivity
2009-10-28  9:59 ` [PATCH 0/5]: " Avi Kivity
2009-10-28 10:13   ` Chris Lalancette
2009-10-28 10:31     ` Avi Kivity
2009-10-29  8:34       ` Chris Lalancette
2009-10-29 10:15         ` Avi Kivity

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=4AE81B36.5010104@redhat.com \
    --to=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.