From: Jan Kiszka <jan.kiszka@web.de>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: uml: pthreads instead of manual clone()?
Date: Sun, 18 Apr 2010 19:50:02 +0200 [thread overview]
Message-ID: <4BCB464A.702@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
Hi Jeff,
is there (still) any reason to use explicit clone() instead of pthreads
to spawn UML kernel threads?
While playing with a patch to finally move os_nsecs to proper
CLOCK_MONOTONIC, I noticed some subtle side-effect: We need to link
against librt for clock_gettime, but that indirectly drags in
libpthread. Now gdb gets unhappy when you try to debug the UML kernel.
It assumes that pthreads are used, but fails to find their IDs and
terminates the session. So the obvious approach appears to be converting
kernel threads to pthreads - if there aren't any know pitfalls.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next reply other threads:[~2010-04-18 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 17:50 Jan Kiszka [this message]
2010-05-17 14:41 ` [uml-devel] uml: pthreads instead of manual clone()? Paolo Giarrusso
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=4BCB464A.702@web.de \
--to=jan.kiszka@web.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 NNTP newsgroup(s).