From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Preemption in Bitmap Scheduler
Date: Wed, 21 Mar 2007 18:45:00 -0000 [thread overview]
Message-ID: <etrucd$aue$2@sea.gmane.org> (raw)
In-Reply-To: <724835.27060.qm@web36215.mail.mud.yahoo.com>
On 2007-03-21, Potdar Smita <sspotdar@yahoo.com> wrote:
> What about preemption?
It works just fine.
> Once a thread begins executing, does it run to completion or
> can it be preempted by a higher priority thread?
The latter.
> Does eCos handle threads created after the system starts
> working?
Of course. There's no way to create a thread before the system
starts working. I have worked with RTOSes where threads could
be declared statically, but eCos doesn't work that way: all
threads are created dynamically.
> If yes, how is this done?
you call cyg_thread_create().
--
Grant Edwards grante Yow! ... I see TOILET
at SEATS...
visi.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-03-21 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 18:33 [ECOS] " Potdar Smita
2007-03-21 18:45 ` Grant Edwards [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='etrucd$aue$2@sea.gmane.org' \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.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).