From: Andrew Parlane <andrewp@carallon.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Spurious interrupt on ARM.
Date: Thu, 31 Oct 2013 17:15:00 -0000 [thread overview]
Message-ID: <52729021.3080205@carallon.com> (raw)
Looking at hal/arm/arch/current/src/vectors.S in IRQ:
We increment the scheduler lock and decrement it again in interrupt_end.
In the case of there being a spurious interrupt, we don't call
interrupt_end, and so the scheduler never gets decremented.
Am I missing something here?
Andrew Parlane
Carallon ltd.
--
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 reply other threads:[~2013-10-31 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 17:15 Andrew Parlane [this message]
2013-11-01 17:06 ` Nick Garnett
2013-11-01 17:20 ` Andrew Parlane
2013-11-01 17:42 ` Nick Garnett
2013-11-01 17:46 ` Andrew Parlane
2013-11-01 17:50 ` Nick Garnett
2013-11-01 17:54 ` Andrew Parlane
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=52729021.3080205@carallon.com \
--to=andrewp@carallon.com \
--cc=ecos-discuss@ecos.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).