From: Richard Henderson <rth@twiddle.net>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
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 07:18:07 -0700 [thread overview]
Message-ID: <7132960a-9a76-b8ee-ec15-f3cfe58a29c1@twiddle.net> (raw)
In-Reply-To: <20170509141336.GF27432@redhat.com>
On 05/09/2017 07:13 AM, Richard W.M. Jones wrote:
> On Tue, May 09, 2017 at 07:05:51AM -0700, Richard Henderson wrote:
>>> 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?
>
> I can see this being useful from virt-what, since it would allow
> vendors to diagnose problems being caused by TCG ...
Thanks, that's an excellent point.
r~
next prev parent reply other threads:[~2017-05-09 14:18 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
2017-05-09 14:13 ` Richard W.M. Jones
2017-05-09 14:18 ` Richard Henderson [this message]
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=7132960a-9a76-b8ee-ec15-f3cfe58a29c1@twiddle.net \
--to=rth@twiddle.net \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).