From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Date: Tue, 01 Oct 2013 08:39:08 +0000 Subject: Re: [PATCH 3/3] KVM: PPC: Book3S: Add support for hwrng found on some powernv systems Message-Id: <20131001083908.GA17294@redhat.com> List-Id: References: <1380177066-3835-1-git-send-email-michael@ellerman.id.au> <1380177066-3835-3-git-send-email-michael@ellerman.id.au> <5243F933.7000907@redhat.com> <20131001083426.GB27484@concordia> In-Reply-To: <20131001083426.GB27484@concordia> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Michael Ellerman Cc: Paolo Bonzini , linux-kernel@vger.kernel.org, Benjamin Herrenschmidt , Paul Mackerras , agraf@suse.de, mpm@selenic.com, herbert@gondor.hengli.com.au, linuxppc-dev@ozlabs.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, tytso@mit.edu On Tue, Oct 01, 2013 at 06:34:26PM +1000, Michael Ellerman wrote: > On Thu, Sep 26, 2013 at 11:06:59AM +0200, Paolo Bonzini wrote: > > Il 26/09/2013 08:31, Michael Ellerman ha scritto: > > > Some powernv systems include a hwrng. Guests can access it via the > > > H_RANDOM hcall. > > > > Is there any reason to do this in the kernel? > > It's less code, and it's faster :) > > > It does not have to be a particularly fast path; > > Sure, but do we have to make it slow on purpose? > We do not put non performance critical devices into the kernel. -- Gleb.