From: "Peter Teoh" <htmldeveloper@gmail.com>
To: Rick Brown <rick.brown.3@gmail.com>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>, linux-newbie@vger.kernel.org
Subject: Re: MIssed interrupts
Date: Fri, 29 Feb 2008 11:35:24 +0800 [thread overview]
Message-ID: <804dabb00802281935q4fbc0988w172b40493883cf1@mail.gmail.com> (raw)
In-Reply-To: <7783925d0802062112r4637c674qf2d1dd356cc0923e@mail.gmail.com>
On 2/7/08, Rick Brown <rick.brown.3@gmail.com> wrote:
> Hi,
>
> If a particual IRQ line has been disabled (disable_irq()), what
> happens if the device on that IRQ line generates interrupt? Does it
> result in missed interrupt?
Yes, and there are a few other problems with interrupts too. For
missed interrupt, we solved by "bottom half". In essence the
interrupt handler has to be very short (which is immuned to another
interrupt trigger), and complete as soon as possible to get ready to
receive another interrupt, while the "deferred context" can execute
slowly, but is all the time interrupt-ready.
>
> And in case of Uniprocessor machine, what happens if interrupts are
> generated while spinlock_irq_save() etc?
>
Same, missed interrupts.
Check this out:
http://www.cs.utah.edu/classes/cs5785/slides/08-6up.pdf
--
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
prev parent reply other threads:[~2008-02-29 3:35 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
2008-03-01 8:36 ` Mulyadi Santosa
2008-02-29 3:35 ` Peter Teoh [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=804dabb00802281935q4fbc0988w172b40493883cf1@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--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