From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933749AbcI3Oqh (ORCPT ); Fri, 30 Sep 2016 10:46:37 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:5291 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933417AbcI3Oq3 (ORCPT ); Fri, 30 Sep 2016 10:46:29 -0400 X-IronPort-AV: E=Sophos;i="5.31,273,1473120000"; d="scan'208";a="389964381" Subject: Re: [Xen-devel] [PATCH] xen: Remove event channel notification through Xen PCI platform device To: KarimAllah Ahmed , , References: <1472248536-2063-1-git-send-email-karahmed@amazon.de> CC: Juergen Gross , Ross Lagerwall , , , Paul Gortmaker , Julien Grall , Vitaly Kuznetsov , "Ingo Molnar" , David Vrabel , "Anthony Liguori" , "H. Peter Anvin" , "Bjorn Helgaas" , Boris Ostrovsky , Thomas Gleixner , Stefano Stabellini From: David Vrabel Message-ID: <57EE7AB7.4020405@citrix.com> Date: Fri, 30 Sep 2016 15:46:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 MIME-Version: 1.0 In-Reply-To: <1472248536-2063-1-git-send-email-karahmed@amazon.de> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-DLP: MIA1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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