[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-arm] [Qemu-devel] [PATCH v5 12/24] hw: acpi: Export the MCFG g
From: |
Samuel Ortiz |
Subject: |
Re: [Qemu-arm] [Qemu-devel] [PATCH v5 12/24] hw: acpi: Export the MCFG getter |
Date: |
Thu, 22 Nov 2018 00:21:06 +0100 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
Hi Igor,
On Thu, Nov 15, 2018 at 01:36:58PM +0100, Igor Mammedov wrote:
> On Mon, 5 Nov 2018 02:40:35 +0100
> Samuel Ortiz <address@hidden> wrote:
>
> > From: Yang Zhong <address@hidden>
> >
> > The ACPI MCFG getter is not x86 specific and could be called from
> > anywhere within generic ACPI API, so let's export it.
> So far it's x86 or more exactly q35 specific thing,
It's property based, and it's using a generic PCIE property afaict.
So it's up to each machine type to define those properties.
I'm curious here: What's the idiomatic way to define a machine
setting/attribute/property, let each instance define it or not, and
make it available at run time?
Would you be getting the PCI host pointer from the ACPI build state and
getting that information back from there?
Cheers,
Samuel.
[Qemu-arm] [PATCH v5 11/24] hw: acpi: Export and generalize the PCI host AML API, Samuel Ortiz, 2018/11/04
[Qemu-arm] [PATCH v5 13/24] hw: acpi: Do not create hotplug method when handler is not defined, Samuel Ortiz, 2018/11/04
[Qemu-arm] [PATCH v5 16/24] hw: acpi: Fix memory hotplug AML generation error, Samuel Ortiz, 2018/11/04
[Qemu-arm] [PATCH v5 14/24] hw: i386: Make the hotpluggable memory size property more generic, Samuel Ortiz, 2018/11/04