From: "H. Peter Anvin" <hpa@zytor.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Andy Lutomirski <luto@amacapital.net>
Cc: X86 ML <x86@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Kees Cook <keescook@chromium.org>, kvm list <kvm@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Gleb Natapov <gleb@kernel.org>, Andrew Honig <ahonig@google.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Daniel Borkmann <dborkman@redhat.com>,
Bandan Das <bsd@redhat.com>, Alok Kataria <akataria@vmware.com>,
virtualization@lists.linux-foundation.org
Subject: Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
Date: Wed, 27 Aug 2014 00:07:32 -0700 [thread overview]
Message-ID: <53FD83B4.1030507@zytor.com> (raw)
In-Reply-To: <53FD81F5.6030701@redhat.com>
On 08/27/2014 12:00 AM, Paolo Bonzini wrote:
> Il 27/08/2014 01:58, Andy Lutomirski ha scritto:
>> hpa pointed out that the ABI that I chose (an MSR from the KVM range
>> and a KVM cpuid bit) is unnecessarily KVM-specific. It would be nice
>> to allocate an MSR that everyone involved can agree on and, rather
>> than relying on a cpuid bit, just have the guest probe for the MSR.
>>
>> This leads to a few questions:
>>
>> 1. How do we allocate an MSR? (For background, this would be an MSR
>> that either returns 64 bits of best-effort cryptographically secure
>> random data or fails with #GP.)
>
> Ask Intel? :)
I'm going to poke around internally. Intel might as a matter of policy
be reluctant to assign an MSR index specifically for software use, but
I'll try to find out.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Andy Lutomirski <luto@amacapital.net>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Kees Cook <keescook@chromium.org>, kvm list <kvm@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Gleb Natapov <gleb@kernel.org>, Andrew Honig <ahonig@google.com>,
Haiyang Zhang <haiyangz@microsoft.com>, X86 ML <x86@kernel.org>,
Bandan Das <bsd@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Daniel Borkmann <dborkman@redhat.com>,
Alok Kataria <akataria@vmware.com>,
virtualization@lists.linux-foundation.org
Subject: Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
Date: Wed, 27 Aug 2014 00:07:32 -0700 [thread overview]
Message-ID: <53FD83B4.1030507@zytor.com> (raw)
In-Reply-To: <53FD81F5.6030701@redhat.com>
On 08/27/2014 12:00 AM, Paolo Bonzini wrote:
> Il 27/08/2014 01:58, Andy Lutomirski ha scritto:
>> hpa pointed out that the ABI that I chose (an MSR from the KVM range
>> and a KVM cpuid bit) is unnecessarily KVM-specific. It would be nice
>> to allocate an MSR that everyone involved can agree on and, rather
>> than relying on a cpuid bit, just have the guest probe for the MSR.
>>
>> This leads to a few questions:
>>
>> 1. How do we allocate an MSR? (For background, this would be an MSR
>> that either returns 64 bits of best-effort cryptographically secure
>> random data or fails with #GP.)
>
> Ask Intel? :)
I'm going to poke around internally. Intel might as a matter of policy
be reluctant to assign an MSR index specifically for software use, but
I'll try to find out.
-hpa
next prev parent reply other threads:[~2014-08-27 7:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 23:58 GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm) Andy Lutomirski
2014-08-26 23:58 ` Andy Lutomirski
2014-08-27 7:00 ` Paolo Bonzini
2014-08-27 7:00 ` Paolo Bonzini
2014-08-27 7:07 ` H. Peter Anvin [this message]
2014-08-27 7:07 ` H. Peter Anvin
2014-08-28 14:17 ` Gleb Natapov
2014-08-28 16:22 ` Andy Lutomirski
2014-08-28 16:22 ` Andy Lutomirski
2014-08-28 19:46 ` Paolo Bonzini
2014-08-28 19:46 ` Paolo Bonzini
2014-08-29 0:13 ` Andy Lutomirski
2014-08-29 0:13 ` Andy Lutomirski
2014-08-29 6:36 ` Paolo Bonzini
2014-08-29 6:36 ` Paolo Bonzini
2014-08-28 14:17 ` Gleb Natapov
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=53FD83B4.1030507@zytor.com \
--to=hpa@zytor.com \
--cc=ahonig@google.com \
--cc=akataria@vmware.com \
--cc=bsd@redhat.com \
--cc=dborkman@redhat.com \
--cc=gleb@kernel.org \
--cc=haiyangz@microsoft.com \
--cc=keescook@chromium.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
--cc=vatsa@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.