From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [PATCH] drivers/net: remove network drivers' last few uses of IRQF_SAMPLE_RANDOM Date: Thu, 15 May 2008 19:33:05 -0400 Message-ID: <20080515233305.GS18825@mit.edu> References: <482C7B18.6060003@garzik.org> <482C7E53.3050300@hp.com> <482C8184.2030906@garzik.org> <482C8550.5000909@intel.com> <482C8D4D.3040702@garzik.org> <20080515214721.GP18825@mit.edu> <482CB1FB.7080807@garzik.org> <20080515222941.GB20976@khazad-dum.debian.net> <482CBCC6.6010905@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Henrique de Moraes Holschuh , Chris Peterson , "Kok, Auke" , Rick Jones , "Brandeburg, Jesse" , Alan Cox , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Jeff Garzik Return-path: Content-Disposition: inline In-Reply-To: <482CBCC6.6010905@garzik.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, May 15, 2008 at 06:44:22PM -0400, Jeff Garzik wrote: > > Neat. I always did prefer VIA padlock in userspace. > > I just sorta assumed a buffering, interrupt-driver TPM RNG driver would be > better than doing it from userspace, but maybe that was a bad assumption to > make on my part. It should be quite doable to support TPM RNG entirely via > userspace, at any rate. If I recall correctly, you need access to a magic TPM key just to *talk* to the TPM. Normally that key is stored in a file, and of course we can have a userspace helper pull that key into the kernel, but given the extensive Trousers infrastructure that can do this already, it seemed to make more sense to do it all in userspace, and not require any more kernel code. - Ted