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 08:04:44 +0200 Message-ID: <541BC77C.6060607@redhat.com> References: <2aa00301e9af4826b5781e01709f81e7@BY2PR0301MB0711.namprd03.prod.outlook.com> <541AEF7D.2010007@zytor.com> <5b9c7dcde3824e49a25f3ee00844b868@BY2PR0301MB0711.namprd03.prod.outlook.com> <541B13B8.1020006@redhat.com> <572ba53a2e1e4278823f718a421e2c1d@BY2PR03MB585.namprd03.prod.outlook.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <572ba53a2e1e4278823f718a421e2c1d@BY2PR03MB585.namprd03.prod.outlook.com> 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: David Hepkin , Andy Lutomirski , Niels Ferguson Cc: Mathew John , Theodore Ts'o , John Starks , kvm list , Gleb Natapov , Linux Virtualization , "H. Peter Anvin" , Jake Oshins List-Id: virtualization@lists.linuxfoundation.org Il 18/09/2014 23:54, David Hepkin ha scritto: > The chief advantage I see to using a hypercall based mechanism is > that it would work across more architectures. MSR's and CPUID's are > specific to X86. If we ever wanted this same mechanism to be > available on an architecture that doesn't support MSR's, a hypercall > based approach would allow for a more consistent mechanism across the > architectures. > > I agree, though, that converging on a common hypercall interface that > would be implemented by all of the hypervisors would likely be much > harder to achieve. There are differences between architectures at the hypercall level, starting with the calling convention. So I don't think it makes much sense to use a hypercall. Paolo