From: Tom Musta <tommusta@gmail.com>
To: Magnus Reftel <reftel@spotify.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] linux-user: Let user specify random seed
Date: Thu, 09 Oct 2014 14:43:24 -0500 [thread overview]
Message-ID: <5436E55C.4070409@gmail.com> (raw)
In-Reply-To: <1412843785-960-1-git-send-email-reftel@spotify.com>
On 10/9/2014 3:36 AM, Magnus Reftel wrote:
> This patch introduces the -seed command line option and the
> QEMU_RAND_SEED environment variable for setting the random seed, which
> is used for the AT_RANDOM ELF aux entry.
>
> This is an updated version of the patch, addressing review comments
> from Eric Blake.
>
Magnus:
Possibly a dumb question: In a regular environment, is there a way for a user to control the 16 bytes of random data pointed to by AT_RANDOM? (I cannot find one).
If not, why is this capability needed in Linux user mode?
next prev parent reply other threads:[~2014-10-09 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 8:36 [Qemu-devel] [PATCH v2] linux-user: Let user specify random seed Magnus Reftel
2014-10-09 8:36 ` [Qemu-devel] [PATCH] " Magnus Reftel
2014-10-09 15:27 ` Eric Blake
2014-10-09 19:10 ` Magnus Reftel
2014-10-09 19:43 ` Tom Musta [this message]
2014-10-10 8:00 ` [Qemu-devel] [PATCH v2] " Magnus Reftel
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=5436E55C.4070409@gmail.com \
--to=tommusta@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=reftel@spotify.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.