From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: inject ExtINT interrupt before APIC interrupts
Date: Thu, 13 Dec 2012 23:06:55 -0200 [thread overview]
Message-ID: <20121214010655.GC17513@amt.cnet> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E2DBDA8@SHSMSX101.ccr.corp.intel.com>
On Wed, Dec 12, 2012 at 12:39:02AM +0000, Zhang, Yang Z wrote:
> Gleb Natapov wrote on 2012-12-10:
> > According to Intel SDM Volume 3 Section 10.8.1 "Interrupt Handling with
> > the Pentium 4 and Intel Xeon Processors" and Section 10.8.2 "Interrupt
> > Handling with the P6 Family and Pentium Processors" ExtINT interrupts are
> > sent directly to the processor core for handling. Currently KVM checks
> > APIC before it considers ExtINT interrupts for injection which is
> > backwards from the spec. Make code behave according to the SDM.
> Ack.
Applied, thanks.
prev parent reply other threads:[~2012-12-14 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 12:05 [PATCH] KVM: inject ExtINT interrupt before APIC interrupts Gleb Natapov
2012-12-12 0:39 ` Zhang, Yang Z
2012-12-14 1:06 ` Marcelo Tosatti [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=20121214010655.GC17513@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yang.z.zhang@intel.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.