From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Liu Shuo <shuo.a.liu@intel.com>, linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
David Vrabel <david.vrabel@citrix.com>,
Ingo Molnar <mingo@kernel.org>,
Anoob Soman <anoob.soman@citrix.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Len Brown <len.brown@intel.com>,
KarimAllah Ahmed <karahmed@amazon.de>,
"moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen/events: Fix interrupt lost during irq_disable and irq_enable
Date: Mon, 31 Jul 2017 09:58:07 -0400 [thread overview]
Message-ID: <7409e669-89b3-42cc-3bb9-93d99a8aef2b@oracle.com> (raw)
In-Reply-To: <1501347598-15084-1-git-send-email-shuo.a.liu@intel.com>
On 07/29/2017 12:59 PM, Liu Shuo wrote:
> Here is a device has xen-pirq-MSI interrupt. Dom0 might lost interrupt
> during driver irq_disable/irq_enable. Here is the scenario,
> 1. irq_disable -> disable_dynirq -> mask_evtchn(irq channel)
> 2. dev interrupt raised by HW and Xen mark its evtchn as pending
> 3. irq_enable -> startup_pirq -> eoi_pirq ->
> clear_evtchn(channel of irq) -> clear pending status
> 4. consume_one_event process the irq event without pending bit assert
> which result in interrupt lost once
> 5. No HW interrupt raising anymore.
>
> Now use enable_dynirq for enable_pirq of xen_pirq_chip to remove
> eoi_pirq when irq_enable.
>
> Signed-off-by: Liu Shuo <shuo.a.liu@intel.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2017-07-31 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 16:59 Liu Shuo
2017-07-31 13:58 ` Boris Ostrovsky [this message]
2017-08-11 14:50 ` Juergen Gross
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=7409e669-89b3-42cc-3bb9-93d99a8aef2b@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=anoob.soman@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=karahmed@amazon.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=shuo.a.liu@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®