linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: prasadr@duettech.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: help on lost interrupt
Date: Fri, 16 Jul 1999 15:12:10 +1000	[thread overview]
Message-ID: <199907160512.PAA24235@tango.anu.edu.au> (raw)
In-Reply-To: <378DE082.B1679C71@duettech.com> (message from Rajendra Prasad on Thu, 15 Jul 1999 18:52:10 +0530)


Rajendra Prasad <prasadr@duettech.com> wrote:

> I was looking the source code of linux for ppc. In the interrupt
> handling
> there is a concept of lost_interrupt and do_lost_interrupt. I could not
> understand why this is required and how it is managed on linux.

With the interrupt controller on powermacs, if you disable an
interrupt in the interrupt controller, then the device requests an
interrupt, then you enable that interrupt in the interrupt controller,
the interrupt controller doesn't then request an interrupt from the
CPU.  So in that situation we set the corresponding bit in
lost_interrupts, and when interrupts get reenabled, we check if there
are any such interrupts that need to be serviced.

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-07-16  5:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-15 13:22 help on lost interrupt Rajendra Prasad
1999-07-16  5:12 ` Paul Mackerras [this message]

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=199907160512.PAA24235@tango.anu.edu.au \
    --to=paulus@cs.anu.edu.au \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=prasadr@duettech.com \
    /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;
as well as URLs for NNTP newsgroup(s).