From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [PATCH v6] hw/i386: pass RNG seed via setup_data entry
Date: Thu, 21 Jul 2022 13:00:59 +0200 [thread overview]
Message-ID: <CAHmME9qTByMDNM-MYcjCPN18eqjAmkT+NJBpPN4SrdVzzQJs7A@mail.gmail.com> (raw)
In-Reply-To: <20220721065744-mutt-send-email-mst@kernel.org>
On Thu, Jul 21, 2022 at 1:00 PM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Thu, Jul 21, 2022 at 12:49:50PM +0200, Jason A. Donenfeld wrote:
> > Tiny machines optimized for fast boot time generally don't use EFI,
> > which means a random seed has to be supplied some other way. For this
> > purpose, Linux (≥5.20) supports passing a seed in the setup_data table
> > with SETUP_RNG_SEED, specially intended for hypervisors, kexec, and
> > specialized bootloaders. The linked commit shows the upstream kernel
> > implementation.
> >
> > Link: https://git.kernel.org/tip/tip/c/68b8e9713c8
> > Cc: Michael S. Tsirkin <mst@redhat.com>
> > Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
> > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > Cc: Richard Henderson <richard.henderson@linaro.org>
> > Cc: Eduardo Habkost <eduardo@habkost.net>
> > Cc: Peter Maydell <peter.maydell@linaro.org>
> > Cc: Philippe Mathieu-Daudé <f4bug@amsat.org>
> > Cc: Laurent Vivier <laurent@vivier.eu>
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
>
> Well why not.
>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>
> who's merging this? Paolo me or you?
How about you go ahead and merge it.
Thanks,
Jason
next prev parent reply other threads:[~2022-07-21 11:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 14:54 [PATCH v3] hw/i386: pass RNG seed via setup_data entry Jason A. Donenfeld
2022-07-19 11:53 ` [PATCH resend " Jason A. Donenfeld
2022-07-20 13:03 ` Jason A. Donenfeld
2022-07-21 9:19 ` Paolo Bonzini
2022-07-21 9:47 ` Jason A. Donenfeld
2022-07-21 9:56 ` Jason A. Donenfeld
2022-07-21 10:09 ` [PATCH v4] " Jason A. Donenfeld
2022-07-21 10:35 ` Michael S. Tsirkin
2022-07-21 10:42 ` Jason A. Donenfeld
2022-07-21 10:47 ` [PATCH v5] " Jason A. Donenfeld
2022-07-21 10:49 ` [PATCH v6] " Jason A. Donenfeld
2022-07-21 11:00 ` Michael S. Tsirkin
2022-07-21 11:00 ` Jason A. Donenfeld [this message]
2022-07-21 11:47 ` Paolo Bonzini
2022-07-21 12:16 ` Jason A. Donenfeld
2022-07-21 12:27 ` Daniel P. Berrangé
2022-07-21 12:41 ` Paolo Bonzini
2022-07-21 12:52 ` Jason A. Donenfeld
2022-07-21 12:56 ` [PATCH v7] " Jason A. Donenfeld
2022-07-21 13:00 ` Paolo Bonzini
2022-07-21 13:00 ` Paolo Bonzini
2022-07-21 13:04 ` Jason A. Donenfeld
2022-07-22 6:10 ` Paolo Bonzini
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=CAHmME9qTByMDNM-MYcjCPN18eqjAmkT+NJBpPN4SrdVzzQJs7A@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=eduardo@habkost.net \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).