From: Keir Fraser <keir.xen@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH v2] x86: re-inject emulated level pirqs in PV on HVM guests if still asserted
Date: Mon, 21 Nov 2011 11:54:32 +0000 [thread overview]
Message-ID: <CAEFEC78.2549A%keir.xen@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1111211106110.31179@kaball-desktop>
On 21/11/2011 11:06, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
wrote:
> On Mon, 21 Nov 2011, Jan Beulich wrote:
>>>>> On 18.11.11 at 12:13, Stefano Stabellini
>>>>> <stefano.stabellini@eu.citrix.com>
>> wrote:
>>> This patch is a backport of CS 24007 for xen-4.1-testing.
>>>
>>> PV on HVM guests can loose level interrupts coming from emulated
>>> devices if they have been remapped onto event channels. The reason is
>>> that we are missing the code to inject a pirq again in the guest when
>>> the guest EOIs it, if it corresponds to an emulated level interrupt
>>> and the interrupt is still asserted.
>>>
>>> Fix this issue and also return error when the guest tries to get the
>>> irq_status of a non-existing pirq.
>>>
>>>
>>> Changes in v2:
>>>
>>> - move the spinlock afterward to cover the new code only.
>>
>> This, as expected, doesn't hang anymore with kernels making use of
>> the PIRQ EOI map.
>
> Thanks for testing!
> Keir, are you happy with the patch?
Yes, I applied it already.
-- Keir
prev parent reply other threads:[~2011-11-21 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 11:13 [PATCH v2] x86: re-inject emulated level pirqs in PV on HVM guests if still asserted Stefano Stabellini
2011-11-18 12:41 ` Pasi Kärkkäinen
2011-11-21 10:53 ` Jan Beulich
2011-11-21 11:06 ` Stefano Stabellini
2011-11-21 11:54 ` Keir Fraser [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=CAEFEC78.2549A%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).