public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why no call to add_interrupt_randomness() on PPC?
Date: 22 Aug 2001 17:26:01 +0200	[thread overview]
Message-ID: <oupitfgnmk6.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <3B83C430.7E5F59C3@nortelnetworks.com.suse.lists.linux.kernel>
In-Reply-To: Chris Friesen's message of "22 Aug 2001 16:44:06 +0200"

Chris Friesen <cfriesen@nortelnetworks.com> writes:

> With all the talk about randomness, I went to see where my current system
> (2.2.19 on PPC) was getting random numbers from.  I was kind of surprised to see
> that there is no call to add_interrupt_randomness() in arch/ppc/kernel/irq.c.
> 
> Does anyone know why this call is not present in ppc_irq_dispatch_handler()? 
> Would it be appropriate for me to make a patch for this?  Who would be the
> appropriate person to send this to?

Nobody except for a few really obscure drivers use SA_SAMPLE_RANDOM
with their interrupt handlers (none on ppc as far as I can see) On
i386 all the gathering is normally done via the keyboard/mouse drivers
and the blk interface. The reason e.g. Macs normally do not gather
entropy is that they're using the new input layer for keyboard and
mouse which for some reason doesn't feed its events into the entropy
pool. I believe Wojtech did a patch for it, but I don't know if it has
been merged into the ppc tree yet.

-Andi

       reply	other threads:[~2001-08-22 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B83C430.7E5F59C3@nortelnetworks.com.suse.lists.linux.kernel>
2001-08-22 15:26 ` Andi Kleen [this message]
2001-08-22 15:37   ` why no call to add_interrupt_randomness() on PPC? Chris Friesen
2001-08-22 15:47     ` Alex Bligh - linux-kernel
2001-08-22 14:39 Chris Friesen

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=oupitfgnmk6.fsf@pigdrop.muc.suse.de \
    --to=ak@suse.de \
    --cc=cfriesen@nortelnetworks.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