From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Munehisa Kamata <kamatam@amazon.com>, david.vrabel@citrix.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Matt Wilson <msw@amazon.com>
Subject: Re: [Xen-devel][PATCH] xen/events: don't migrate disabled IRQs
Date: Fri, 20 May 2016 17:32:12 -0400 [thread overview]
Message-ID: <573F825C.5000401@oracle.com> (raw)
In-Reply-To: <1463779324-12225-1-git-send-email-kamatam@amazon.com>
On 05/20/2016 05:22 PM, Munehisa Kamata wrote:
> Commit ff1e22e7a638 ("xen/events: Mask a moving irq") introduced
> a crash below. This can be triggered after being resumed from suspend
> (e.g. live migration) if there are disabled IRQs with
> IRQD_SETAFFINITY_PENDING set.
A patch just like this has been submitted recently
(http://lists.xenproject.org/archives/html/xen-devel/2016-05/msg00956.html)
and should go in soon.
Thanks.
-boris
next prev parent reply other threads:[~2016-05-20 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 21:22 [Xen-devel][PATCH] xen/events: don't migrate disabled IRQs Munehisa Kamata
2016-05-20 21:32 ` Boris Ostrovsky [this message]
2016-05-20 22:13 ` Munehisa Kamata
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=573F825C.5000401@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=kamatam@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msw@amazon.com \
--cc=stable@vger.kernel.org \
--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