From: Sergei Slobodov <sslobodov@caracal-tech.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] interrupts always enabled in scheduler
Date: Tue, 16 Jan 2001 14:45:00 -0000 [thread overview]
Message-ID: <3A64CEAE.4060300@caracal-tech.com> (raw)
Hi,
I'm new to this list, sorry if the question has been answered (I did
search through the archives first, without success).
I'm looking through the sources, trying to determine whether we should
try to use ecos or port our own kernel from another platform, and there
is at least one major issue I don't understand. ECOS seems to support
nested interrupts, yet there is no interrupt enable/disable pair around
the code that manipulates thread queues, such as Cyg_Thread::resume(),
which non-atomically changes global scheduler structures. Woudn't it
cause data corruption if a higher priority interrupt occurs in the
middle of resume() call?
Please enlighten me!
Regards,
Sergei Slobodov
Caracal Consulting Inc.
next reply other threads:[~2001-01-16 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 14:45 Sergei Slobodov [this message]
2001-01-16 17:19 ` Jonathan Larmour
2001-01-16 20:31 ` Sergei Slobodov
2001-01-16 23:04 ` Jonathan Larmour
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=3A64CEAE.4060300@caracal-tech.com \
--to=sslobodov@caracal-tech.com \
--cc=ecos-discuss@sourceware.cygnus.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).