Re: [Qemu-devel] Memory API: handling unassigned physical memory

[Andreas Färber]

Am 30.04.2012 16:55, schrieb Mark Cave-Ayland:
> Note that if properties can't be set by the caller after construction,
> then I'm effectively going to have to copy the entire esp_init()
> function;

The idea would be to use the QOM way of creating the object, using QOM
and/or custom ways to set properties/fields and then "realize" it. The
infrastructure for the latter is still missing, so for now you would
split the esp_init function into one part that goes to the call sites
and an esp_realize function that gets called for any remaining part
after the appropriate properties and MMIO mappings have been set up.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg