qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] per-machine vs per-qemu-version compat_props macros (wa


From: Eduardo Habkost
Subject: Re: [Qemu-devel] per-machine vs per-qemu-version compat_props macros (was Re: acpi:ich9: add memory hotplug handling)
Date: Tue, 24 Jun 2014 21:18:22 -0300
User-agent: Mutt/1.5.23 (2014-03-12)

On Tue, Jun 24, 2014 at 11:30:04PM +0100, Peter Maydell wrote:
> On 24 June 2014 18:55, Eduardo Habkost <address@hidden> wrote:
> > On Tue, Jun 24, 2014 at 05:47:53PM +0100, Peter Maydell wrote:
> >> What if different machines in a particular release had the
> >> property set to different defaults?
> >
> > I never saw that happen, and I don't think it is even likely: default
> > values set in instance_init, and compat_props are applied just after
> > instance_init, before object_new() returns. So a machine-type would need
> > to find a way to change fields after instance_init but before
> > compat_props are applied.
> 
> OK, yes, that's not going to happen. I had thought they were
> applied at the same point as -global settings.

They are. -global settings are also set just after instance_init, and
before object_new() returns. Internally, compat_props are translated to
global properties.

-- 
Eduardo



reply via email to

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