From: Jeff Garzik <jgarzik@pobox.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] RNG rewrite...
Date: Mon, 17 Oct 2005 19:26:41 -0400 [thread overview]
Message-ID: <43543331.6030603@pobox.com> (raw)
In-Reply-To: <dj1bb5$riu$1@terminus.zytor.com>
H. Peter Anvin wrote:
> Followup to: <20051016005341.GB5946@plexity.net>
> By author: Deepak Saxena <dsaxena@plexity.net>
> In newsgroup: linux.dev.kernel
>
>>It's a magic regsiter we just read/write and could be done in userspace.
>>I also took a look at MPC85xx and it has the same sort of interface but
>>also has an error interrupt capability. On second thought a class
>>interface is overkill b/c there will only be one RNG per system, so
>>I can just do something like watchdogs where we have a bunch of simple
>>drivers exposing the same interface. We could do it in user space but
>>then we have separate RNG implementations for x86 and !x86 and I'd
>>rather not see that. Can we move the x86 code out to userspace and
>>just let the daemon eat the numbers directly from HW? We can mmap()
>>PCI devices, but I don't know enough about x86 to say whether msr
>>instructions can execute out of userspace (or if we want them to...).
> MSR instructions cannot execute out of userspace, but the MSR driver
> might be possible to use. It's usually quite slow, however.
MSRs are used for setup, not for actual data.
Intel: magic MMIO address (readb)
AMD: magic PIO address (inl)
VIA: CPU instruction ('xstore')
Jeff
next prev parent reply other threads:[~2005-10-17 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 4:31 [RFC] RNG rewrite Deepak Saxena
2005-10-15 10:40 ` Jeff Garzik
2005-10-16 0:53 ` Deepak Saxena
2005-10-17 23:15 ` H. Peter Anvin
2005-10-17 23:26 ` Jeff Garzik [this message]
2005-10-18 0:22 ` H. Peter Anvin
2005-10-17 23:31 ` Jeff Garzik
2005-10-18 1:00 ` Deepak Saxena
2005-10-18 1:05 ` Deepak Saxena
2005-10-18 1:09 ` Jeff Garzik
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=43543331.6030603@pobox.com \
--to=jgarzik@pobox.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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