linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: pthreads?
Date: Tue, 16 Sep 2003 20:44:41 +0200	[thread overview]
Message-ID: <200309162044.41268.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <1063623075.2123.9.camel@henrik.marasystems.com>

Alle 12:51, lunedì 15 settembre 2003, Henrik Nordstrom ha scritto:
> 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.
There is(from long time) the idea to make possible turning UML into a library.
This means that solving this issue in UML is worthwhile. I.e., let's suppose 
that the malloc's conflict. Then, Uml will use uml_malloc, which will be is 
own version, and everyone will be happy. Using a -Dmalloc=uml_malloc would 
make unnecessary changing the source. This is a quick idea(and details about 
the exact names are to be tuned), but I hope it's useful.
-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN



-------------------------------------------------------
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

  reply	other threads:[~2003-09-16 18:43 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
2003-09-16 18:44                     ` BlaisorBlade [this message]
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=200309162044.41268.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --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