From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Daniel Borkmann <dborkman@redhat.com>,
kvm list <kvm@vger.kernel.org>, "Theodore Ts'o" <tytso@mit.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>, X86 ML <x86@kernel.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/4] random,x86,kvm: Add and use MSR_KVM_GET_RNG_SEED
Date: Wed, 16 Jul 2014 14:36:56 -0700 [thread overview]
Message-ID: <53C6F078.4000201@zytor.com> (raw)
In-Reply-To: <CALCETrX4MVbkmMejQ6O_-Wt_uKDfR1K=XGnb3_59w-hmzV++iA@mail.gmail.com>
On 07/16/2014 02:32 PM, Andy Lutomirski wrote:
>
> On the theory that I see no legitimate reason to expose this to guest
> user space, I think we shouldn't expose it. If we wanted to add a
> get_random_bytes syscall, that would be an entirely different story,
> though.
>
> Should I send v3 as one series or should I split it into host and guest parts?
>
It doesn't matter... as long as they are separate *patches*.
-hpa
prev parent reply other threads:[~2014-07-16 21:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 2:48 [PATCH 0/4] random,x86,kvm: Add and use MSR_KVM_GET_RNG_SEED Andy Lutomirski
2014-07-16 2:48 ` [PATCH 1/4] x86,kvm: Add MSR_KVM_GET_RNG_SEED and a matching feature bit Andy Lutomirski
2014-07-16 2:48 ` [PATCH 2/4] random,x86: Add arch_get_slow_rng_u64 Andy Lutomirski
2014-07-16 2:48 ` [PATCH 3/4] random: Seed pools from arch_get_slow_rng_u64 at startup Andy Lutomirski
2014-07-16 2:48 ` [PATCH 4/4] x86,kaslr: Use MSR_KVM_GET_RNG_SEED for KASLR if available Andy Lutomirski
2014-07-16 6:41 ` [PATCH 0/4] random,x86,kvm: Add and use MSR_KVM_GET_RNG_SEED Gleb Natapov
2014-07-16 7:10 ` Daniel Borkmann
2014-07-16 7:23 ` Gleb Natapov
2014-07-16 7:36 ` Paolo Bonzini
2014-07-16 14:07 ` Andy Lutomirski
2014-07-16 14:32 ` Paolo Bonzini
2014-07-16 14:53 ` Gleb Natapov
2014-07-16 15:56 ` Andy Lutomirski
2014-07-16 16:03 ` H. Peter Anvin
2014-07-16 16:08 ` Paolo Bonzini
2014-07-16 16:13 ` H. Peter Anvin
2014-07-16 16:21 ` Gleb Natapov
2014-07-16 20:20 ` H. Peter Anvin
2014-07-16 21:32 ` Andy Lutomirski
2014-07-16 21:36 ` H. Peter Anvin [this message]
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=53C6F078.4000201@zytor.com \
--to=hpa@zytor.com \
--cc=dborkman@redhat.com \
--cc=gleb@kernel.org \
--cc=keescook@chromium.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox