qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
	qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] target-i386: Disable CPUID_EXT_MONITOR when KVM is enabled
Date: Sat, 25 May 2013 08:25:49 +0200	[thread overview]
Message-ID: <51A0596D.1050300@redhat.com> (raw)
In-Reply-To: <jpg8v33kg5k.fsf@redhat.com>

Il 25/05/2013 03:21, Bandan Das ha scritto:
> There is one user-visible effect: "-cpu ...,enforce" will stop failing
> because of missing KVM support for CPUID_EXT_MONITOR. But that's exactly
> the point: there's no point in having CPU model definitions that would
> never work as-is with neither TCG or KVM. This patch is changing the
> meaning of (e.g.) "-machine ...,accel=kvm -cpu Opteron_G3" to match what
> was already happening in practice.

But then -cpu Opteron_G3 does not match a "real" Opteron G3.  Is it
worth it?

Paolo

  reply	other threads:[~2013-05-25  6:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  1:13 [Qemu-devel] [PATCH] target-i386: Disable CPUID_EXT_MONITOR when KVM is enabled Bandan Das
2013-05-25  1:21 ` Bandan Das
2013-05-25  6:25   ` Paolo Bonzini [this message]
2013-05-27 12:09     ` Eduardo Habkost
2013-05-27 12:21       ` Paolo Bonzini
2013-05-27 13:07         ` Eduardo Habkost
2013-05-27 13:14           ` Paolo Bonzini
2013-05-27 13:32             ` Eduardo Habkost
2013-05-28 16:34           ` Bandan Das
2013-05-28 16:46             ` Paolo Bonzini
2013-05-28 16:48               ` Andreas Färber
2013-05-29 14:31                 ` Eduardo Habkost

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=51A0596D.1050300@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=bsd@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).