From: Alistair Francis <alistair23@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] hw/riscv: virt: pass random seed to fdt
Date: Fri, 8 Jul 2022 17:59:18 +1000 [thread overview]
Message-ID: <CAKmqyKNUC+eiXLqqwSC3AjmqUtBc8p59mAHdumZ2oHiCT8aT0A@mail.gmail.com> (raw)
In-Reply-To: <YsYxM6gmJf7y/nJc@zx2c4.com>
On Thu, Jul 7, 2022 at 11:04 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hey Alistair,
>
> On Tue, Jul 05, 2022 at 03:09:09AM +0200, Jason A. Donenfeld wrote:
> > Hi Alistair,
> >
> > On Wed, Jun 29, 2022 at 4:09 AM Alistair Francis <alistair23@gmail.com> wrote:
> > > I have a Linux 5.8 test case that is failing due to this patch.
> >
> > Before I started fixing things in random.c, there were a lot of early
> > boot bugs with the RNG in Linux. I backported the fixes for these to
> > all stable kernels. It's a bummer that risc-v got hit by these bugs,
> > but I think that's just the way things go unfortunately.
Hmm... That's a pain. So there is a bug in older kernels where they
won't boot if we specify this?
Can you point to the fixes?
> >
> > Jason
> >
>
> By the way, I still can't find this in your github tree. I was hoping we
> could get this in for 7.1.
Yeah, it's hard to accept when it will break users. I would rather
avoid someone upgrading to QEMU 7.1 and the kernel failing to boot
with no information.
>
> As for your 5.8 issue, I've been trying to reproduce that to understand
> more about it, but I'm unable to. I've been trying with
> nommu_virt_defconfig using my patch ontop of qemu master. Maybe it's
> possible in testing this out you were testing the wrong branch? Anyway,
> it'd be nice to get this queued up...
Hmm... you can't reproduce it?
Alistair
>
> Jason
next prev parent reply other threads:[~2022-07-08 8:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 11:58 [PATCH] hw/riscv: virt: pass random seed to fdt Jason A. Donenfeld
2022-06-15 4:05 ` Bin Meng
2022-06-16 2:32 ` Alistair Francis
2022-06-16 10:01 ` Jason A. Donenfeld
2022-06-16 12:17 ` Alistair Francis
2022-06-29 2:09 ` Alistair Francis
2022-07-05 1:09 ` Jason A. Donenfeld
2022-07-07 1:04 ` Jason A. Donenfeld
2022-07-08 7:59 ` Alistair Francis [this message]
2022-07-08 9:56 ` Jason A. Donenfeld
2022-07-11 0:25 ` Alistair Francis
2022-07-11 0:27 ` Jason A. Donenfeld
2022-07-11 3:36 ` Alistair Francis
2022-07-11 16:45 ` Jason A. Donenfeld
2022-07-13 17:29 ` Jason A. Donenfeld
2022-07-18 22:39 ` Alistair Francis
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=CAKmqyKNUC+eiXLqqwSC3AjmqUtBc8p59mAHdumZ2oHiCT8aT0A@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=Jason@zx2c4.com \
--cc=alistair.francis@wdc.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;
as well as URLs for NNTP newsgroup(s).