[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v4] Hvmloader: Modify ACPI to only supply _EJ0 methods for PCIslots that support hotplug by runtime patching
- To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
- From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
- Date: Fri, 9 May 2014 17:12:13 +0100
- Cc: "Huangweidong \(C\)" <weidong.huang@xxxxxxxxxx>, "Gonglei \(Arei\)" <arei.gonglei@xxxxxxxxxx>, "mst@xxxxxxxxxx" <mst@xxxxxxxxxx>, "Hanweidong \(Randy\)" <hanweidong@xxxxxxxxxx>, "qemu-devel@xxxxxxxxxx" <qemu-devel@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, "fabio.fantoni@xxxxxxx" <fabio.fantoni@xxxxxxx>, Anthony Perard <anthony.perard@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, "kevin@xxxxxxxxxxxx" <kevin@xxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxx>, Ross Philipson <ross.philipson@xxxxxxxxxx>, "johannes.krampf@xxxxxxxxxxxxxx" <johannes.krampf@xxxxxxxxxxxxxx>, "Gaowei \(UVP\)" <gao.gaowei@xxxxxxxxxx>, Paul Durrant <Paul.Durrant@xxxxxxxxxx>
- Delivery-date: Fri, 09 May 2014 16:12:27 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Fri, 2014-05-09 at 12:00 -0400, Konrad Rzeszutek Wilk wrote:
> So we could just then gat the _EJ0 functionality based on values that
> are present (or not) in the SSDT ?
AIUI the very presence of _EJ0 is what marks the device as being
ejectable (e.g. in the Windows device manager).
It would be possible to make _EJ0 conditionally turn itself into a NOP
without resorting to an SSDT, but I don't think that solves the issue
they are trying to solve, which is that the user can even try to eject
an non-hotplug device. (grep for UAR1 in our dsdt.asl and
acpi_info->com1_present in hvmloader/acpi/build.c for an example of this
sort of conditional thing)
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
