Re: [Qemu-devel] [PATCH RFC 00/13] qemu: generate acpi tables for the guest

[Peter Maydell]

On 14 May 2013 10:29, Gerd Hoffmann <address@hidden> wrote:
> Anthony wrote:
>> and is also a good
>> reason why exposing this information via a common interface (fw_cfg)
>> would be a good idea.
>
> Huh?  As far I know we generate device trees in qemu

It depends. For ARM we insist that the user provides the
device tree that corresponds to the kernel they're going to
run, and then we just tweak it a bit. (For the upcoming
'mach-virt' pure-virtual hardware we're going to end up
generating a device tree completely from scratch, though.)

Not sure fw_cfg is particularly relevant though -- for
device tree the obvious "nice" way to do it would be
to have the device tree generating/modifying code able
to walk the QOM object tree introspecting it to identify
hardware presence and properties. That's probably not
doable today though. (I need to look more closely at
PPC device tree handling, really.)

thanks
-- PMM