From: Henrik Nordstrom <hno@marasystems.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jeff Dike <jdike@addtoit.com>,
User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Re: pthreads?
Date: 15 Sep 2003 12:51:15 +0200 [thread overview]
Message-ID: <1063623075.2123.9.camel@henrik.marasystems.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0309151127130.3302-100000@vervain.sonytel.be>
mån 2003-09-15 klockan 11.28 skrev Geert Uytterhoeven:
> No, UML only _uses_ those symbols, libpthread redefines them in a way that
> breaks UML.
uml redefines several libc symbols which does conflict with pthreads.
The most notable is that uml overrides malloc/free but I think there is
also a few other overrides due to kernel library calls having the same
name as their libc equivalent calls. If you are to link with pthreads
each of these must be verified to be threads safe to the same level as
their libc/pthreads counterpart. On the positive side most kernel lib
calls most likely are threads safe due to the multithreaded nature of
the kernel, but any lib call making use of locking or other kernel
constructs will almost certainly fail or cause problems if ever invoked
from a pthread.
Regards
Henrik
--
Henrik Nordstrom <hno@marasystems.com>
MARA Systems AB
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-09-15 10:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 15:54 [uml-devel] pthreads? Geert Uytterhoeven
2003-09-11 17:55 ` Jeff Dike
2003-09-12 8:52 ` [uml-devel] pthreads? Gerd Knorr
2003-09-12 9:07 ` Geert Uytterhoeven
2003-09-12 11:08 ` Gerd Knorr
2003-09-12 11:18 ` Geert Uytterhoeven
2003-09-12 12:15 ` Gerd Knorr
2003-09-12 12:17 ` Geert Uytterhoeven
2003-09-12 11:18 ` Henrik Nordstrom
2003-09-12 16:28 ` Jeff Dike
2003-09-12 22:25 ` Henrik Nordstrom
2003-09-13 18:53 ` Jeff Dike
2003-09-13 21:01 ` Henrik Nordstrom
2003-09-13 15:24 ` Geert Uytterhoeven
2003-09-13 18:54 ` Jeff Dike
2003-09-15 6:57 ` Geert Uytterhoeven
2003-09-15 9:19 ` Henrik Nordstrom
2003-09-15 9:28 ` Geert Uytterhoeven
2003-09-15 10:51 ` Henrik Nordstrom [this message]
2003-09-16 18:44 ` BlaisorBlade
2003-10-02 9:20 ` Jan Hudec
2003-10-02 9:08 ` Jan Hudec
2003-10-02 9:24 ` Geert Uytterhoeven
2003-10-02 9:31 ` Jan Hudec
[not found] ` <Pine.GSO.4.21.0310021146500.8567-100000@vervain.sonytel.be>
2003-10-02 13:52 ` Jan Hudec
2003-10-02 14:28 ` Geert Uytterhoeven
2003-10-02 14:42 ` Jan Hudec
2003-10-07 15:51 ` The Story Continues (was: Re: [uml-devel] Re: pthreads?) Geert Uytterhoeven
2003-10-11 1:48 ` Jeff Dike
2003-10-11 8:39 ` Geert Uytterhoeven
2003-10-12 9:53 ` Geert Uytterhoeven
2003-10-06 13:29 ` [uml-devel] Re: pthreads? BlaisorBlade
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 12:30 stian
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=1063623075.2123.9.camel@henrik.marasystems.com \
--to=hno@marasystems.com \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--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