From: "Peter Teoh" <htmldeveloper@gmail.com>
To: Jike Song <albcamus@gmail.com>,
Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: Rick Brown <rick.brown.3@gmail.com>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-newbie@vger.kernel.org
Subject: Re: MIssed interrupts
Date: Fri, 29 Feb 2008 22:34:49 +0800 [thread overview]
Message-ID: <804dabb00802290634u3873bcb5m7be4a80856d76de7@mail.gmail.com> (raw)
In-Reply-To: <df9815e70802282321l789d6c3bj967da63d3761183b@mail.gmail.com>
Hi Mulyadi,
On Fri, Feb 29, 2008 at 3:21 PM, Jike Song <albcamus@gmail.com> wrote:
> On Thu, Feb 7, 2008 at 11:50 PM, Mulyadi Santosa
> <mulyadi.santosa@gmail.com> wrote:
> > Hi....
> >
> > AFAIK at the time it's in disabled state...yes it will be missed. But
> > once you enabled it again.... missing interrupts will be received.
>
> Do you mean that the PIC(Local APIC or something else) will retain the
> disabled interrupt, and deliver it once again to the processor core as
> soon as be re-enabled?
>
This is something new to me. After some some search, Mulyadi is
right. It is called "Interrupt Request Buffering". And according to
Unabridged Pentium 4 (pg 1537) while processing one interrupt, it can
receive another interrupt, but the 3rd one that comes in will be
discarded, and it is all on the same interrupt vector. Thanks for
the sharing everyone....
> Regards,
> Jike
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2008-02-29 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 5:12 MIssed interrupts Rick Brown
2008-02-07 15:50 ` Mulyadi Santosa
2008-02-29 7:21 ` Jike Song
2008-02-29 11:43 ` Mulyadi Santosa
2008-03-03 1:10 ` Jike Song
2008-04-02 8:09 ` Peter Teoh
2008-02-29 14:34 ` Peter Teoh [this message]
2008-03-01 8:36 ` Mulyadi Santosa
2008-02-29 3:35 ` Peter Teoh
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=804dabb00802290634u3873bcb5m7be4a80856d76de7@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=albcamus@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--cc=mulyadi.santosa@gmail.com \
--cc=rick.brown.3@gmail.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