From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] How to cancel a Xenomai POSIX thread
Date: Mon, 10 Dec 2007 22:56:55 +0100 [thread overview]
Message-ID: <18269.46631.20493.787763@domain.hid> (raw)
In-Reply-To: <475DB21C.8040800@domain.hid>
Wolfgang Grandegger wrote:
> Gilles Chanteperdrix wrote:
> > On Dec 10, 2007 4:20 PM, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> Gilles Chanteperdrix wrote:
> >>> Wolfgang Grandegger wrote:
> >> # ./kill_pthread
> >> Starting high_prio_task
> >> low_prio_task: policy=1 prio=10
> >> Killed low_prio task: count=172709970, overruns=0
> >>
> >> [1]+ Stopped ./kill_pthread
> >
> > What you are observing is probably a difference between linuxthreads
> > and NPTL: with linuxthreads, SIGSTOP can be sent to a particular
> > thread and will cause this thread only to stop. With NPTL, it seems
> > that the effect of SIGSTOP is global, it affects the entire process. I
> > will test tonight on my x86 box to see if I observe the same effect.
>
> Ah, the man page says:
>
> Note that pthread_kill() only causes the signal to be handled in the
> context of the given thread; the signal action (termination or stop-
> ping) affects the process as a whole.
I can confirm the same effect on plain Linux. So, the newly added
pthread_kill is not to blame (yet).
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2007-12-10 21:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 12:31 [Xenomai-core] How to cancel a Xenomai POSIX thread Wolfgang Grandegger
2007-12-06 13:13 ` Gilles Chanteperdrix
2007-12-06 13:24 ` Wolfgang Grandegger
2007-12-06 13:28 ` Gilles Chanteperdrix
2007-12-06 13:44 ` Gilles Chanteperdrix
2007-12-06 14:05 ` Wolfgang Grandegger
2007-12-06 14:21 ` Gilles Chanteperdrix
2007-12-07 14:03 ` Wolfgang Grandegger
2007-12-07 21:23 ` Gilles Chanteperdrix
2007-12-07 22:10 ` Gilles Chanteperdrix
2007-12-09 21:55 ` Wolfgang Grandegger
2007-12-09 22:52 ` Gilles Chanteperdrix
2007-12-10 7:27 ` Wolfgang Grandegger
2007-12-10 15:20 ` Wolfgang Grandegger
2007-12-10 15:55 ` Gilles Chanteperdrix
2007-12-10 21:39 ` Wolfgang Grandegger
2007-12-10 21:46 ` Wolfgang Grandegger
2007-12-11 13:20 ` Wolfgang Grandegger
2007-12-11 13:23 ` Gilles Chanteperdrix
2007-12-11 14:39 ` Wolfgang Grandegger
2007-12-11 19:59 ` Gilles Chanteperdrix
2007-12-12 7:56 ` Wolfgang Grandegger
2007-12-12 9:07 ` Gilles Chanteperdrix
2007-12-12 9:59 ` Wolfgang Grandegger
2007-12-12 20:08 ` Gilles Chanteperdrix
2007-12-12 21:00 ` Wolfgang Grandegger
2007-12-12 21:48 ` Gilles Chanteperdrix
2007-12-10 21:56 ` Gilles Chanteperdrix [this message]
2007-12-10 21:21 ` Gilles Chanteperdrix
2007-12-10 21:37 ` Wolfgang Grandegger
2007-12-10 22:11 ` Gilles Chanteperdrix
2007-12-11 7:45 ` Wolfgang Grandegger
2007-12-06 13:47 ` Wolfgang Grandegger
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=18269.46631.20493.787763@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=wg@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.