[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support

From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support
Date: Mon, 10 Jun 2013 20:25:15 -0500

Hi Kevin,

On Mon, Jun 10, 2013 at 8:19 PM, Kevin O'Connor <address@hidden> wrote:
> On Mon, Jun 10, 2013 at 07:51:55PM -0500, Anthony Liguori wrote:
>> I think that we can pretty much touch a table once pulling all of the
>> info from QOM and then from a SeaBIOS point of view, never have to
>> touch it again.
> Thanks.  I do think it would help if you could go through the details
> of a couple of tables and a couple of DSDT entries and walk through
> where each field will come from.  And also describe how seabios will
> build the resulting AML.  From my previous email:
>> I'm quite curious how you are planning to solve (a).  I think it would
>> help move this conversation forward if you could take a couple acpi
>> tables in use today (eg, madt, srat) and describe the future format
>> and location for each field in those tables.  I think it would also be
>> useful if you could do the same for a couple DSDT entries (eg,
>> \_SB.PCI0, \_SB.PCI0.ISA) and also describe how you plan to have the
>> guest build the AML from that info.
> I do understand your desire to pass this stuff as parameters, but I
> really don't see it as feasible.  I'm hoping that if you can write up
> some examples with specifics you'll either enlighten me or you'll see
> the difficulties I'm trying to describe.

Is your basic argument that generating these tables is hard, QEMU can
and should just hard code them and change them whenever it feels like
without involving SeaBIOS?

If that's what it boils down to, I'll look more closely at it.


Anthony Liguori

> -Kevin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]