From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
qemu-devel@nongnu.org, Jiaxun Yang <jiaxun.yang@flygoat.com>,
Aurelien Jarno <aurelien@aurel32.net>,
kvm-devel <kvm@vger.kernel.org>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v2] mips/malta: pass RNG seed to to kernel via env var
Date: Tue, 4 Oct 2022 09:05:35 +0100 [thread overview]
Message-ID: <YzvpT67iJMMR9n25@redhat.com> (raw)
In-Reply-To: <b529059a-7819-e49d-e4dc-7ae79ee21ec5@amsat.org>
On Tue, Oct 04, 2022 at 12:36:03AM +0200, Philippe Mathieu-Daudé wrote:
> Hi Jason,
>
> Per https://www.qemu.org/docs/master/devel/submitting-a-patch.html#when-resending-patches-add-a-version-tag:
>
> Send each new revision as a new top-level thread, rather than burying it
> in-reply-to an earlier revision, as many reviewers are not looking inside
> deep threads for new patches.
>
> On 3/10/22 12:36, Jason A. Donenfeld wrote:
> > As of the kernel commit linked below, Linux ingests an RNG seed
> > passed from the hypervisor. So, pass this for the Malta platform, and
> > reinitialize it on reboot too, so that it's always fresh.
> >
> > Cc: Philippe Mathieu-Daudé <f4bug@amsat.org>
> > Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>
> > Cc: Aurelien Jarno <aurelien@aurel32.net>
> > Link: https://git.kernel.org/mips/c/056a68cea01
>
> You seem to justify this commit by the kernel commit, which justifies
> itself mentioning hypervisor use... So the egg comes first before the
> chicken.
The kernel justification is that the guest OS needs a good RNG
seed. The kernel patch is just saying that the firmware / hypervisor
side is where this seed generally expected to come from. This is
fine, and not notably different from what Jason's already got
wired up for the various other targets in QEMU.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2022-10-04 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YziPyCqwl5KIE2cf@zx2c4.com>
[not found] ` <20221003103627.947985-1-Jason@zx2c4.com>
2022-10-03 22:36 ` [PATCH v2] mips/malta: pass RNG seed to to kernel via env var Philippe Mathieu-Daudé
2022-10-03 23:07 ` Jason A. Donenfeld
2022-10-04 10:37 ` Jason A. Donenfeld
2022-10-04 10:53 ` Peter Maydell
2022-10-04 10:56 ` Jason A. Donenfeld
2022-10-04 11:00 ` Jason A. Donenfeld
2022-10-04 11:03 ` Peter Maydell
2022-10-04 11:10 ` Jason A. Donenfeld
2022-10-04 11:39 ` BALATON Zoltan
2022-10-04 12:08 ` Jason A. Donenfeld
2022-10-04 8:05 ` Daniel P. Berrangé [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=YzvpT67iJMMR9n25@redhat.com \
--to=berrange@redhat.com \
--cc=Jason@zx2c4.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.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