From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Andy Lutomirski <luto@amacapital.net>,
Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: Mathew John <mathewj@microsoft.com>,
Theodore Ts'o <tytso@mit.edu>, Jim Mattson <jmattson@vmware.com>,
kvm list <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
Niels Ferguson <niels@microsoft.com>,
David Hepkin <davidhep@microsoft.com>,
Doug Covelli <dcovelli@vmware.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jake Oshins <jakeo@microsoft.com>,
xen-devel@lists.xenproject.org,
Alok Kataria <akataria@vmware.com>,
John Starks <John.Starks@microsoft.com>
Subject: Re: [Xen-devel] [RFC] Hypervisor RNG and enumeration
Date: Wed, 29 Oct 2014 09:07:53 -0700 [thread overview]
Message-ID: <545110D9.6000703@zytor.com> (raw)
In-Reply-To: <5450C35D.1030907@citrix.com>
On 10/29/2014 03:37 AM, Andrew Cooper wrote:
>>
>> CPUID with EAX = 0x4F000001 and ECX >= N MUST return all zeros.
>>
>> To the extent that the hypervisor prefers a given interface, it should
>> specify that interface earlier in the list. For example, KVM might place
>> its "KVMKVMKVM" signature first in the list to indicate that it should be
>> used by guests in preference to other supported interfaces. Other hypervisors
>> would likely use a different order.
>>
>> The exact semantics of the ordering of the list is beyond the scope of
>> this specification.
>
> How do you evaluate N?
>
> It would make more sense for CPUID.4F000001[ECX=0] to return N in one
> register, and perhaps "prefered interface index" in another. The
> signatures can then be obtained from CPUID.4F000001[ECX={1 to N}].
>
> That way, a consumer can be confident that they have found all the
> signatures, without relying on an unbounded loop and checking for zeroes
Yes. Specifically, it should return it in EAX. That is the preferred
interface and we are trying to push for that going forward.
-hpa
next prev parent reply other threads:[~2014-10-29 16:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 5:19 [RFC] Hypervisor RNG and enumeration Andy Lutomirski
2014-10-29 10:37 ` [Xen-devel] " Andrew Cooper
2014-10-29 13:45 ` Paolo Bonzini
2014-10-29 13:57 ` David Vrabel
2014-10-29 14:01 ` Paolo Bonzini
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:23 ` Andy Lutomirski
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:07 ` H. Peter Anvin [this message]
2014-10-29 15:14 ` Ian Jackson
2014-10-29 16:13 ` Andy Lutomirski
2014-10-29 16:29 ` Jake Oshins
2014-10-29 16:50 ` Andy Lutomirski
2014-10-29 18:22 ` Paolo Bonzini
2014-10-30 12:21 ` David Vrabel
2014-10-30 12:25 ` Paolo Bonzini
2014-10-30 14:45 ` Andy Lutomirski
2014-10-30 15:12 ` Ian Campbell
2014-10-30 14:33 ` Roger Pau Monné
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=545110D9.6000703@zytor.com \
--to=hpa@zytor.com \
--cc=John.Starks@microsoft.com \
--cc=akataria@vmware.com \
--cc=andrew.cooper3@citrix.com \
--cc=davidhep@microsoft.com \
--cc=dcovelli@vmware.com \
--cc=gleb@kernel.org \
--cc=jakeo@microsoft.com \
--cc=jmattson@vmware.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mathewj@microsoft.com \
--cc=niels@microsoft.com \
--cc=pbonzini@redhat.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.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).