[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d17d56ce-4ea2-abef-a20d-f7e31a9a06bf@oracle.com>
Date: Fri, 14 Apr 2017 09:58:54 -0400
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Greg KH <greg@...ah.com>, Juergen Gross <jgross@...e.com>
Cc: stable@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Stefano Stabellini <stefano.stabellini@...citrix.com>,
Julien Grall <julien.grall@...rix.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Ross Lagerwall <ross.lagerwall@...rix.com>,
xen-devel@...ts.xenproject.org, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org, Anthony Liguori <aliguori@...zon.com>,
KarimAllah Ahmed <karahmed@...zon.de>
Subject: Re: [stable-4.9: PATCH] xen: revert commit 72a9b186292
On 04/14/2017 05:17 AM, Greg KH wrote:
> On Thu, Apr 13, 2017 at 03:06:53PM +0200, Juergen Gross wrote:
>> Revert commit 72a9b186292 ("xen: Remove event channel notification
>> through Xen PCI platform device") as the original analysis was wrong
>> that all the removed code isn't in use any more.
>>
>> It is still necessary for old Xen versions (< 4.0) and for being able
>> to run the Linux kernel as dom0 in a nested Xen environment.
> What is the commit id of this revert in Linus's tree?
It hasn't been reverted in Linus tree yet --- there were some changes in
Xen code in 4.11 that make the revert not a mechanical operation and we
are somewhat hesitant to have a patch this late in the release cycle.
-boris
Powered by blists - more mailing lists