From: David Vrabel <david.vrabel@citrix.com>
To: KarimAllah Ahmed <karahmed@amazon.de>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
<linux-pci@vger.kernel.org>, <x86@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Julien Grall <julien.grall@citrix.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
"Ingo Molnar" <mingo@redhat.com>,
David Vrabel <david.vrabel@citrix.com>,
"Anthony Liguori" <aliguori@amazon.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH] xen: Remove event channel notification through Xen PCI platform device
Date: Fri, 30 Sep 2016 15:46:15 +0100 [thread overview]
Message-ID: <57EE7AB7.4020405@citrix.com> (raw)
In-Reply-To: <1472248536-2063-1-git-send-email-karahmed@amazon.de>
On 26/08/16 22:55, KarimAllah Ahmed wrote:
> Ever since commit 254d1a3f02eb ("xen/pv-on-hvm kexec: shutdown watches
> from old kernel") using the INTx interrupt from Xen PCI platform device for
> event channel notification would just lockup the guest during bootup.
> postcore_initcall now calls xs_reset_watches which will eventually try to read
> a value from XenStore and will get stuck on read_reply at XenBus forever since
> the platform driver is not probed yet and its INTx interrupt handler is not
> registered yet. That means that the guest can not be notified at this moment of
> any pending event channels and none of the per-event handlers will ever be
> invoked (including the XenStore one) and the reply will never be picked up by
> the kernel.
Applied to for-linus-4.9, thanks.
David
next prev parent reply other threads:[~2016-09-30 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472248536-2063-1-git-send-email-karahmed@amazon.de>
2016-08-29 17:29 ` [PATCH] xen: Remove event channel notification through Xen PCI platform device Boris Ostrovsky
2016-09-30 14:46 ` David Vrabel [this message]
2017-04-10 12:28 ` [Xen-devel] " Raslan, KarimAllah
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=57EE7AB7.4020405@citrix.com \
--to=david.vrabel@citrix.com \
--cc=aliguori@amazon.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=julien.grall@citrix.com \
--cc=karahmed@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=ross.lagerwall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).