From: Randy <randyqiuxy@hotmail.com>
To: Randy <randyqiuxy@hotmail.com>, "Stanislav Meduna" <stano@meduna.org>
Cc: "eCos Discussion" <ecos-discuss@sourceware.org>
Subject: [ECOS] why did not enable interrupt before call pending dsr while not use interrupt stack
Date: Thu, 18 Apr 2013 02:50:00 -0000 [thread overview]
Message-ID: <BLU0-SMTP10224AA77F3616B1084389EC3CF0@phx.gbl> (raw)
In-Reply-To: <BLU0-SMTP14119AC133E089A26AE1335C3C30@phx.gbl>
Hi all,
I see that enable interrupt before call pending dsr while we use interrupt stack, but I don't find anywhere do the same thing if we don't use interrupt stack via MACRO:CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK
If we don't enable interrupt before calling pending dsr, then calling simple synchronization methods like cyg_semaphore_post() in DSR would cause problem since the methods will be scheduling..
Anything wrong with my understanding?
--------------
Thanks a lot..
Best regards,
Randy
prev parent reply other threads:[~2013-04-18 2:50 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
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 ` Randy [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=BLU0-SMTP10224AA77F3616B1084389EC3CF0@phx.gbl \
--to=randyqiuxy@hotmail.com \
--cc=ecos-discuss@sourceware.org \
--cc=stano@meduna.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 read-only IMAP folder(s) and NNTP newsgroup(s).