On Tue, Oct 11, 2022 at 2:06 PM Jason A. Donenfeld wrote:
>
> On Tue, Oct 11, 2022 at 09:46:01AM +0300, Pavel Dovgalyuk wrote:
> > On 10.10.2022 18:32, Peter Maydell wrote:
> > > On Mon, 10 Oct 2022 at 16:21, Jason A. Donenfeld wrote:
> > >>
> > >> On Mon, Oct 10, 2022 at 11:54:50AM +0100, Peter
On Tue, Oct 11, 2022 at 09:46:01AM +0300, Pavel Dovgalyuk wrote:
> On 10.10.2022 18:32, Peter Maydell wrote:
> > On Mon, 10 Oct 2022 at 16:21, Jason A. Donenfeld wrote:
> >>
> >> On Mon, Oct 10, 2022 at 11:54:50AM +0100, Peter Maydell wrote:
> >>> The error is essentially the record-and-replay sub
On 10.10.2022 18:32, Peter Maydell wrote:
On Mon, 10 Oct 2022 at 16:21, Jason A. Donenfeld wrote:
On Mon, Oct 10, 2022 at 11:54:50AM +0100, Peter Maydell wrote:
The error is essentially the record-and-replay subsystem saying "the
replay just asked for a random number at point when the recordi
On Mon, Oct 10, 2022 at 04:32:45PM +0100, Peter Maydell wrote:
> On Mon, 10 Oct 2022 at 16:21, Jason A. Donenfeld wrote:
> >
> > On Mon, Oct 10, 2022 at 11:54:50AM +0100, Peter Maydell wrote:
> > > The error is essentially the record-and-replay subsystem saying "the
> > > replay just asked for a r
On Mon, 10 Oct 2022 at 16:21, Jason A. Donenfeld wrote:
>
> On Mon, Oct 10, 2022 at 11:54:50AM +0100, Peter Maydell wrote:
> > The error is essentially the record-and-replay subsystem saying "the
> > replay just asked for a random number at point when the recording
> > did not ask for one, and so
On Mon, Oct 10, 2022 at 11:54:50AM +0100, Peter Maydell wrote:
> The error is essentially the record-and-replay subsystem saying "the
> replay just asked for a random number at point when the recording
> did not ask for one, and so there's no 'this is what the number was'
> info in the record".
>
On Mon, 10 Oct 2022 at 11:54, Peter Maydell wrote:
>
> On Thu, 6 Oct 2022 at 14:16, Peter Maydell wrote:
> >
> > On Fri, 30 Sept 2022 at 00:23, Jason A. Donenfeld wrote:
> > >
> > > When the system reboots, the rng-seed that the FDT has should be
> > > re-randomized, so that the new boot gets a
On Thu, 6 Oct 2022 at 14:16, Peter Maydell wrote:
>
> On Fri, 30 Sept 2022 at 00:23, Jason A. Donenfeld wrote:
> >
> > When the system reboots, the rng-seed that the FDT has should be
> > re-randomized, so that the new boot gets a new seed. Several
> > architectures require this functionality, so
Hi Peter,
On Thu, Oct 6, 2022 at 7:16 AM Peter Maydell wrote:
>
> On Fri, 30 Sept 2022 at 00:23, Jason A. Donenfeld wrote:
> >
> > When the system reboots, the rng-seed that the FDT has should be
> > re-randomized, so that the new boot gets a new seed. Several
> > architectures require this func
On Fri, 30 Sept 2022 at 00:23, Jason A. Donenfeld wrote:
>
> When the system reboots, the rng-seed that the FDT has should be
> re-randomized, so that the new boot gets a new seed. Several
> architectures require this functionality, so export a function for
> injecting a new seed into the given FD
On Fri, Sep 30, 2022 at 7:24 AM Jason A. Donenfeld wrote:
>
> When the system reboots, the rng-seed that the FDT has should be
> re-randomized, so that the new boot gets a new seed. Several
> architectures require this functionality, so export a function for
> injecting a new seed into the given F
11 matches
Mail list logo