linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: the ppc_n_lost_interrupts thing...
Date: Thu, 27 Jan 2000 18:35:56 -0800	[thread overview]
Message-ID: <3891008C.A83C47B4@mvista.com> (raw)


Hi, all,

I am a newbie to PowerPC-linux.  Hopefully this question is
not too dumb.

When I looked into the interrupt related code in ppc-linux,
I got totally confused by the "ppc_n_lost_interrupts"
variable.

Here is the comment from pmac_pic.c file :

        /*
         * Unfortunately, setting the bit in the enable register
         * when the device interrupt is already on *doesn't* set
         * the bit in the flag register or request another
interrupt.
         */

>From this, I can infer that ppc_n_lost_interrupts is used to
"fake" a new interrupt at the end of an interrupt handling.
However,
what I don't understand is - how could this possibly detect an
interrupt that happens while the CPU is blocking external
interrupt?
In this case, ppc_n_lost_interrupts won't be incremented and when
the external interrupt is re-enabled, we won't be able to get
into interrupt mode.

That does not sound right to me.  Could someone shed a light on
this whole "ppc_n_lost_interrupt" thing?  Thanks in advance.


Jun

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-01-28  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-28  2:35 Jun Sun [this message]
2000-01-28 10:21 ` the ppc_n_lost_interrupts thing Benjamin Herrenschmidt
2000-02-02 23:38   ` Jun Sun

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=3891008C.A83C47B4@mvista.com \
    --to=jsun@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).