public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Randy <randyqiuxy@hotmail.com>
To: "eCos Discussion" <ecos-discuss@sourceware.org>
Subject: [ECOS] why should ISR arrange that the same interrupt would not recur until DSR completed?
Date: Sun, 31 Mar 2013 08:08:00 -0000	[thread overview]
Message-ID: <BLU0-SMTP3646F7EEA8206EF237E9FD3C3DD0@phx.gbl> (raw)
In-Reply-To: <51546EFC.5050603@dallaway.org.uk>

Hi all,
eCos reference tells me that "In order to allow DSRs to run with interrupts enabled, the ISR for a particular interrupt source (or the hardware) must arrange that that interrupt will not recur until the DSR has completed." 
But why? If other interrupt could be enable when processing DSR, why is the same interrupt not  allowed?
Let's image what happened if it comes some interrupt(same interrupt source or not)  when it process DSR, 
1) re-enter "__default_interrupt_vsr ", save registers(context of interrupted DSR), increase cyg_scheduler_sched_lock, disable interrupt, call ISR
2) call interrupt_end which will post dsr into dsr-list, enable interrupt and call pending dsrs and then schedule..
Anything wrong for this work-flow?
Thanks for your advance..

Thanks a lot..
Best regards,
Randy

  parent reply	other threads:[~2013-03-31  8:08 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   ` Randy [this message]
2013-03-31 12:06     ` [ECOS] why should ISR arrange that the same interrupt would not recur until DSR completed? 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                     ` [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=BLU0-SMTP3646F7EEA8206EF237E9FD3C3DD0@phx.gbl \
    --to=randyqiuxy@hotmail.com \
    --cc=ecos-discuss@sourceware.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).