qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/2] Support CPUID signature for TCG
Date: Tue, 9 May 2017 15:08:46 +0100	[thread overview]
Message-ID: <20170509140846.GK1669@redhat.com> (raw)
In-Reply-To: <040c1e25-224f-1a8a-9f60-7238e6ad5df6@twiddle.net>

On Tue, May 09, 2017 at 07:05:51AM -0700, Richard Henderson wrote:
> On 05/09/2017 06:27 AM, Daniel P. Berrange wrote:
> > This enables report of a signature in CPUID for the TCG
> > interpretor.
> > 
> > Changed in v4:
> > 
> >   - Report 0x40000001 in EAX for 0x40000000 index (Eduardo)
> >   - Report all zeros for 0x40000001 index (Eduardo)
> >   - Make code style consistent when checking limits (Eduardo)
> > 
> > Changed in v3:
> > 
> >   - Simplify CPU limit code still further (Eduardo)
> > 
> > Changed in v2:
> > 
> >   - Rewrite the way we bounds check / cap the CPUID index
> >     to use a flat switch, instead of nested ifs (Eduardo)
> >   - Add a 'tcg-cpuid' property to allow it to be hidden
> >     (Eduardo)
> >   - Hide the TCG signature for old machine types
> >   - Force code to a no-op if tcg_enabled() is false (Eduardo)
> > 
> > 
> > NB, I did not introduce a general 'hypervisor-cpuid' property
> > to obsolete the existing 'kvm=off|on' -cpu property, since it
> > appears impossible to get the back compat semantics right,
> > as described in a previous reply.
> > 
> > Daniel P. Berrange (2):
> >    i386: rewrite way CPUID index is validated
> >    i386: expose "TCGTCGTCGTCG" in the 0x40000000 CPUID leaf
> 
> I probably should have commented earlier but...  what's the point?
> 
> If you want the guest os to actually do anything with this, what do
> you gain for advertising TCG over KVM?

TCG doesn't expose any of the paravirt features that KVM does, so from that
POV reporting "KVMKVMKVM" when running TCG would be wrong. As mentioned in
the 2nd patch too, every hypervisor out there reports a distinct CPUID
string, so again I think TCG should have its own identity, as it is
different CPU emulation other users of QEMU (Xen, KVM, $whatever Windows
and OS-X CPU accelerators are).

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-05-09 14:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 13:27 [Qemu-devel] [PATCH v4 0/2] Support CPUID signature for TCG Daniel P. Berrange
2017-05-09 13:27 ` [Qemu-devel] [PATCH v4 1/2] i386: rewrite way CPUID index is validated Daniel P. Berrange
2017-05-19 14:58   ` Kashyap Chamarthy
2017-05-19 19:43     ` Eduardo Habkost
2017-05-09 13:27 ` [Qemu-devel] [PATCH v4 2/2] i386: expose "TCGTCGTCGTCG" in the 0x40000000 CPUID leaf Daniel P. Berrange
2017-05-09 14:05 ` [Qemu-devel] [PATCH v4 0/2] Support CPUID signature for TCG Richard Henderson
2017-05-09 14:08   ` Daniel P. Berrange [this message]
2017-05-09 14:13   ` Richard W.M. Jones
2017-05-09 14:18     ` Richard Henderson
2017-05-19 19:41       ` Eduardo Habkost
2017-05-19 19:51         ` Richard W.M. Jones
2017-05-19 19:51         ` Richard W.M. Jones
2017-06-14 10:18         ` Daniel P. Berrange
2017-06-20 12:02           ` Eduardo Habkost
2017-05-09 20:12     ` 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=20170509140846.GK1669@redhat.com \
    --to=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).