From: Stanislav Meduna <stano@meduna.org>
To: randyqiuxy <randyqiuxy@hotmail.com>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] why should ISR arrange that the same interrupt would not recur until DSR completed?
Date: Sun, 31 Mar 2013 12:06:00 -0000 [thread overview]
Message-ID: <5158269C.5000804@meduna.org> (raw)
In-Reply-To: <BLU0-SMTP3646F7EEA8206EF237E9FD3C3DD0@phx.gbl>
On 31.03.2013 10:10, Randy wrote:
> But why? If other interrupt could be enable when processing DSR, why
> is the same interrupt not allowed?
1) Other interrupt does not need to synchronize access to the hardware
and/or data structures shared between the ISR and corresponding DSR.
Remember, neither the ISR nor DSR can block. Disabling interrupts
outside of interrupt handlers is generally frowned upon.
2) The list of pending DSRs is now upper bounded. With the same
interrupt enabled it would become unbounded.
Regards
--
Stano
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-03-31 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 14:40 [ECOS] Is eCosPro a fork of eCos? Liam Knight
2013-03-28 16:25 ` [ECOS] " John Dallaway
2013-03-28 18:40 ` Liam Knight
2013-03-31 8:08 ` [ECOS] why should ISR arrange that the same interrupt would not recur until DSR completed? Randy
2013-03-31 12:06 ` Stanislav Meduna [this message]
2013-03-31 14:48 ` Randy
2013-04-01 11:59 ` Stanislav Meduna
2013-04-07 12:05 ` Randy
2013-04-07 13:21 ` Stanislav Meduna
2013-04-10 8:36 ` [ECOS] put unmask in ISR rather than DSR causing interrupt lost Randy
2013-04-10 9:27 ` 回复: " Randy
2013-04-14 11:39 ` 回复: " Randy
2013-04-18 2:50 ` [ECOS] why did not enable interrupt before call pending dsr while not use interrupt stack Randy
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=5158269C.5000804@meduna.org \
--to=stano@meduna.org \
--cc=ecos-discuss@sourceware.org \
--cc=randyqiuxy@hotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).