On Thu, 27 Apr 2017 13:59:08 -0600
Bruce Rogers wrote:
> Commit f0c9d64a exposed the issue that with a xenfv machine using
> pci passthrough, acpi cpi hotplug code was being executed by mistake.
s/cpi/pci/
> Guard calls to acpi_pcihp_device_plug_cb (and corresponding
> acpi_pcihp_device_unplug_c
On Thu, 27 Apr 2017 14:09:11 -0700 (PDT)
Stefano Stabellini wrote:
> On Thu, 27 Apr 2017, Bruce Rogers wrote:
> > Commit f0c9d64a exposed the issue that with a xenfv machine using
> > pci passthrough, acpi cpi hotplug code was being executed by mistake.
> > Guard calls to acpi_pcihp_device_plug_c
On Thu, 27 Apr 2017, Bruce Rogers wrote:
> >>> On 4/27/2017 at 03:09 PM, Stefano Stabellini
> >>> wrote:
> > On Thu, 27 Apr 2017, Bruce Rogers wrote:
> >> Commit f0c9d64a exposed the issue that with a xenfv machine using
> >> pci passthrough, acpi cpi hotplug code was being executed by mistake.
>>> On 4/27/2017 at 03:09 PM, Stefano Stabellini
>>> wrote:
> On Thu, 27 Apr 2017, Bruce Rogers wrote:
>> Commit f0c9d64a exposed the issue that with a xenfv machine using
>> pci passthrough, acpi cpi hotplug code was being executed by mistake.
>> Guard calls to acpi_pcihp_device_plug_cb (and
On Thu, 27 Apr 2017, Bruce Rogers wrote:
> Commit f0c9d64a exposed the issue that with a xenfv machine using
> pci passthrough, acpi cpi hotplug code was being executed by mistake.
> Guard calls to acpi_pcihp_device_plug_cb (and corresponding
> acpi_pcihp_device_unplug_cb) with a check for xen_enab
Commit f0c9d64a exposed the issue that with a xenfv machine using
pci passthrough, acpi cpi hotplug code was being executed by mistake.
Guard calls to acpi_pcihp_device_plug_cb (and corresponding
acpi_pcihp_device_unplug_cb) with a check for xen_enabled(). Without
this check I am seeing an error th
