qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Igor Mammedov <imammedo@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
	Juan Quintela <quintela@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call minutes July 31th
Date: Tue, 31 Jul 2012 18:16:00 +0200	[thread overview]
Message-ID: <501804C0.4040500@suse.de> (raw)
In-Reply-To: <1887466189.22829081.1343750784007.JavaMail.root@redhat.com>

Am 31.07.2012 18:06, schrieb Igor Mammedov:
> ----- Original Message -----
>> From: "Eduardo Habkost" <ehabkost@redhat.com>
>> To: "Juan Quintela" <quintela@redhat.com>, "Anthony Liguori" <anthony@codemonkey.ws>
>> Cc: qemu-devel@nongnu.org, "KVM devel mailing list" <kvm@vger.kernel.org>
>> 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! :)

Andreas

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

      reply	other threads:[~2012-07-31 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 14:32 [Qemu-devel] KVM call minutes July 31th Juan Quintela
2012-07-31 15:14 ` [Qemu-devel] QEMU CPU model versioning/compatibility (was Re: KVM call minutes July 31th) Eduardo Habkost
2012-08-01  8:50   ` Avi Kivity
2012-07-31 15:40 ` [Qemu-devel] KVM call minutes July 31th Eduardo Habkost
2012-07-31 15:56   ` Andreas Färber
2012-07-31 16:06   ` Igor Mammedov
2012-07-31 16:16     ` Andreas Färber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=501804C0.4040500@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).