From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Shohei Fujiwara <fujiwara-sxa@necst.nec.co.jp>,
Qing He <qing.he@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0/6] MSI-INTx interrupt translation for HVM
Date: Sun, 01 Mar 2009 14:55:21 +0000 [thread overview]
Message-ID: <C5D05259.3AB4%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20090227113753.6A27.CB716985@necst.nec.co.jp>
On 27/02/2009 02:41, "Shohei Fujiwara" <fujiwara-sxa@necst.nec.co.jp> wrote:
> I found hypervisor doesn't issue EOI before injecting the
> interrupt to guest domain, if MSI isn't maskable.
> The 2nd interrupt may be lost. What do you think about this?
The second interrupt should not be lost! It should be marked in the local
APIC's IRR bitmap and should hence cause an interrupt to fire as soon as the
in-service interrupt is EOIed (and hence cleared from the local APIC's ISR
bitmap).
Are you thus *sure* this is really the root-cause of your problem?
Could it be that the MSI *is* maskable, and that masking/unmasking loses
interrupt messages, for example?
-- Keir
next prev parent reply other threads:[~2009-03-01 14:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 9:06 [PATCH 0/6] MSI-INTx interrupt translation for HVM Qing He
2009-01-08 9:06 ` [PATCH 1/6] passthrough: MSI-INTx " Qing He
2009-01-08 9:06 ` [PATCH 2/6] ioemu:passthrough: MSI-INTx interrupt translation support Qing He
2009-01-08 9:06 ` [PATCH 3/6] pci: add pci option support for XML-RPC server Qing He
2009-01-08 9:06 ` [PATCH 4/6] pci: add pci option support for XenAPI server Qing He
2009-01-08 9:06 ` [PATCH 5/6] pci: add config options for MSI-INTx translation in HVM Qing He
2009-01-08 9:06 ` [PATCH 6/6] passthough: MSI-INTx translation documentation Qing He
2009-01-08 10:44 ` [PATCH 0/6] MSI-INTx interrupt translation for HVM Shohei Fujiwara
2009-01-08 14:52 ` Qing He
2009-01-09 4:26 ` Shohei Fujiwara
2009-01-09 6:57 ` Qing He
2009-01-13 9:05 ` Shohei Fujiwara
2009-01-13 9:28 ` Qing He
2009-01-14 6:39 ` Shohei Fujiwara
2009-01-14 7:38 ` Qing He
2009-01-14 8:26 ` Shohei Fujiwara
2009-01-14 9:17 ` Qing He
2009-01-15 2:35 ` Shohei Fujiwara
2009-01-15 6:25 ` Qing He
2009-01-16 4:34 ` Shohei Fujiwara
2009-02-27 2:41 ` Shohei Fujiwara
2009-03-01 14:55 ` Keir Fraser [this message]
2009-03-02 7:19 ` Shohei Fujiwara
2009-03-02 8:47 ` Keir Fraser
2009-03-02 9:24 ` Qing He
2009-03-02 9:40 ` Keir Fraser
2009-03-02 10:27 ` Shohei Fujiwara
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=C5D05259.3AB4%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=fujiwara-sxa@necst.nec.co.jp \
--cc=qing.he@intel.com \
--cc=xen-devel@lists.xensource.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.