From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Standardizing an MSR or other hypercall to get an RNG seed? Date: Fri, 19 Sep 2014 18:22:24 +0200 Message-ID: <541C5840.10205@redhat.com> References: <541B13B8.1020006@redhat.com> <1969371640.51211843.1411066715223.JavaMail.zimbra@redhat.com> <0180a8dfcad746a895755c4374853c16@BY2PR03MB585.namprd03.prod.outlook.com> <541B5553.7020203@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: "Nakajima, Jun" , Andy Lutomirski Cc: Mathew John , Theodore Ts'o , John Starks , kvm list , Gleb Natapov , Niels Ferguson , Linux Virtualization , David Hepkin , "H. Peter Anvin" , Jake Oshins List-Id: virtualization@lists.linuxfoundation.org Il 19/09/2014 18:14, Nakajima, Jun ha scritto: > For example, > - CPUID 0x48000001.EAX would return the feature presence (e.g. in > EBX), and the result in EDX:EAX (if present) at the same time, or > - CPUID 0x48000001.EAX would return the feature presence only, and > CPUID 0x48000002.EAX (acts like a hypercall) returns up to 4 32-bit > values. The latter is much better, because an "unknown" CPUID will return the value of the highest leaf below 0x80000000, and conflicts can happen easily. Paolo