From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-ppc@nongnu.org, agraf@suse.de, david@gibson.dropbear.id.au
Cc: qemu-devel@nongnu.org, kvm-ppc@vger.kernel.org,
michael@ellerman.id.au, amit.shah@redhat.com,
sam.bobroff@au1.ibm.com, gkurz@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3] ppc/spapr: Implement H_RANDOM hypercall in QEMU
Date: Fri, 11 Sep 2015 05:29:09 -0600 [thread overview]
Message-ID: <55F2BB05.1050809@redhat.com> (raw)
In-Reply-To: <1441963021-31423-1-git-send-email-thuth@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
On 09/11/2015 03:17 AM, Thomas Huth wrote:
> The PAPR interface defines a hypercall to pass high-quality
> hardware generated random numbers to guests. Recent kernels can
> already provide this hypercall to the guest if the right hardware
> random number generator is available. But in case the user wants
> to use another source like EGD, or QEMU is running with an older
> kernel, we should also have this call in QEMU, so that guests that
> do not support virtio-rng yet can get good random numbers, too.
>
> This patch now adds a new pseude-device to QEMU that either
s/pseude/pseudo/
> directly provides this hypercall to the guest or is able to
> enable the in-kernel hypercall if available. The in-kernel
> hypercall can be enabled with the use-kvm property, e.g.:
>
> qemu-system-ppc64 -device spapr-rng,use-kvm=true
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-09-11 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 9:17 [Qemu-devel] [PATCH v3] ppc/spapr: Implement H_RANDOM hypercall in QEMU Thomas Huth
2015-09-11 11:29 ` Eric Blake [this message]
2015-09-14 2:15 ` David Gibson
2015-09-14 6:32 ` Thomas Huth
2015-09-15 4:26 ` David Gibson
2015-09-15 10:24 ` Amit Shah
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=55F2BB05.1050809@redhat.com \
--to=eblake@redhat.com \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.bobroff@au1.ibm.com \
--cc=thuth@redhat.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 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).