public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Paleologos Spanos <paleolog@ee.ucla.edu>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Thread states
Date: Tue, 09 Jan 2001 16:55:00 -0000	[thread overview]
Message-ID: <3A5BB308.A21EE034@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10101091545400.18211-100000@sierra.ee.ucla.edu>

Paleologos Spanos wrote:
> 
>  Hi,I have a question regarding the state of thread.
> 
> -When a thread finishes its work what is its state? the "EXITED"?
>  The question is if the "exited" state is  showing that the thread has
> finished execution or it is the state after having exit(with the exit
> function) the thread?

The former - although from your description the latter would imply the
former anyway?

> -If I want to stop the execution of a thread and then start it again from
> the beggining again(not from the point it stopped) which
> are the appropriate functions? exit and then resume,or kill and then
> resume?

I think you are a bit confused: you call cyg_thread_exit() to exit the
calling thread; you call cyg_thread_kill() to request another thread exits.

When the thread exits you can call cyg_thread_resume() on it.
 
> -Will this thread be present on the wait_queue of the bitmap
> scheduler?(assuming that we have the bitmap scheduler)

At what point?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

  reply	other threads:[~2001-01-09 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 16:00 Paleologos Spanos
2001-01-09 16:55 ` Jonathan Larmour [this message]
2001-01-10  0:17   ` Paleologos Spanos
2001-01-10  3:30     ` Nick Garnett
2001-01-10  9:08     ` Jonathan Larmour
2001-04-12 14:28 Paleologos Spanos
2001-04-13  9:27 Paleologos Spanos
2001-04-17 12:46 Paleologos Spanos
2001-04-17 15:55 ` 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=3A5BB308.A21EE034@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=paleolog@ee.ucla.edu \
    /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).