[Top][All Lists]

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

Re: [Qemu-devel] KVM call minutes July 31th

From: Andreas Färber
Subject: Re: [Qemu-devel] KVM call minutes July 31th
Date: Tue, 31 Jul 2012 18:16:00 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0

Am 31.07.2012 18:06, schrieb Igor Mammedov:
> ----- Original Message -----
>> From: "Eduardo Habkost" <address@hidden>
>> To: "Juan Quintela" <address@hidden>, "Anthony Liguori" <address@hidden>
>> Cc: address@hidden, "KVM devel mailing list" <address@hidden>
>> Sent: Tuesday, July 31, 2012 5:40:14 PM
>> Subject: Re: [Qemu-devel] KVM call minutes July 31th
>> On Tue, Jul 31, 2012 at 04:32:05PM +0200, Juan Quintela wrote:
>>> - 1.2 plans for CPU model versioning/compatibility (eduardo)
>>>   (global properties vs QOM vs qdev)
>>>   how to do it ?  configuration file?  moving back to the code?
>>>   different external interface from internal one
>> Another question:
>> Anthony, you  mentioned that you had a series to convert the CPU to
>> be
>> actual qdev device objects. Do you have a pointer for it? I couldn't
>> find it.
> it was http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg03847.html
> but there is another earlier proposal by Andreas to make CPU as DEVICE only
> for softmmu targets. 
> So consensus wasn't reached yet.
> If we are to to use global props creating CPU subclasses, we might have to
> make CPU as DEVICE for *-user target as well and pull in qdev deps into it.

We don't version the user emulators, so there's no compatibility
properties to set if we follow the machine versioning scheme.
I expect Nehalem to resolve to Nehalem-1.2 but there's no strict need to
have a Nehalem-1.1 since there's no concept of migration.

Anything involving qdev in *-user will not make it in time for 1.2! :)


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

reply via email to

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