From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45940) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TTZGT-0004xA-Nj for qemu-devel@nongnu.org; Wed, 31 Oct 2012 10:27:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TTZGN-0006Wq-CO for qemu-devel@nongnu.org; Wed, 31 Oct 2012 10:27:29 -0400 Received: from mail-pb0-f45.google.com ([209.85.160.45]:50004) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TTZGM-0006WU-Q3 for qemu-devel@nongnu.org; Wed, 31 Oct 2012 10:27:23 -0400 Received: by mail-pb0-f45.google.com with SMTP id rp2so982988pbb.4 for ; Wed, 31 Oct 2012 07:27:20 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <50913542.5020608@redhat.com> Date: Wed, 31 Oct 2012 15:27:14 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <604401631.2277495.1351264128301.JavaMail.root@redhat.com> <871ugl44v5.fsf@codemonkey.ws> <508AB5C0.2000304@zytor.com> <508ADD66.5040909@redhat.com> <5ea4bbfb-b761-42ef-93f8-7c91fee0bb30@email.android.com> <508AE9A6.4060304@redhat.com> <508AF2C0.30404@zytor.com> <508E4215.6050803@redhat.com> <508F5B07.8070008@zytor.com> <508F9847.6030702@redhat.com> <50904273.5040401@zytor.com> <5090D36C.9080807@redhat.com> <50913273.5010502@zytor.com> In-Reply-To: <50913273.5010502@zytor.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/6] add paravirtualization hwrng support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "H. Peter Anvin" Cc: Amit Shah , Anthony Liguori , Andreas Faerber , qemu-devel@nongnu.org Il 31/10/2012 15:15, H. Peter Anvin ha scritto: >> >> Related to this, rdrand's "entropy content" in the worst case will be >> only 1/255th of the data it produces: Intel documents that one 256-bit >> seed will result in up to 1022 64-bit random numbers. Yet, it is good >> enough to drive rngd. Would it make sense for QEMU to implement the >> same kind of stretching of /dev/random data, to avoid depleting the >> host's entropy pool too fast? >> > > Absolutely not; in fact, we have to do data reduction in rngd for > exactly this reason (and a Qemu backend would have to do the same). > There is a new RDSEED instruction in newer CPUs to correct this. Ok, thanks. At least I asked. :) Paolo