All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeff Dike <jdike@addtoit.com>
Cc: Gerd Knorr <kraxel@bytesex.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: uml-patch-2.6.0
Date: Mon, 19 Jan 2004 09:28:05 +0100	[thread overview]
Message-ID: <20040119082805.GA4412@elte.hu> (raw)
In-Reply-To: <20040119075351.GA4088@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> > 2.4 UMLs work fine with these libcs.  I had been assuming (without any
> > evidence) that there was some other capability check (like uname), and
> > libc gets horribly confused when it sees a 2.6 kernel that doesn't
> > have the thread_info stuff.
> 
> ok, i talked to Ulrich, and it turns out that ld.so in Fedora uses the
> set_tid_address() syscall to find out whether the kernel has NPTL or
> not [and thus whether to use the TLS glibc or the standard one]. [...]

unfortunately, this is only the case if the kernel is below 2.5.69 and
has 'nptl' in the uname. Otherwise ld.so assumes full NPTL support.

so the only compatible solution seems to be to implement
set/get_thread_area() within UML. Since UML itself is linked statically,
which causes the non-TLS glibc to be linked, i think it should be safe
to just shadow the TLS descriptors in the UML process and call
set_thread_area() for every new thread that has TLS descriptors not
equal to the previous thread's TLS descriptors.

but wrt. LinuxThreads - it doesnt seem UML skas mode implements LDT
state properly - does it?

	Ingo


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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:[~2004-01-19  8:27 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  5:05 [uml-devel] uml-patch-2.6.0 Jeff Dike
2004-01-13  5:05 ` uml-patch-2.6.0 Jeff Dike
2004-01-13  5:18 ` [uml-devel] uml-patch-2.6.0 Jeff Dike
2004-01-13  5:18   ` uml-patch-2.6.0 Jeff Dike
2004-01-13 10:19 ` [uml-devel] uml-patch-2.6.0 Sven Köhler
2004-01-13 10:19   ` uml-patch-2.6.0 Sven Köhler
2004-01-13 18:55   ` [uml-devel] uml-patch-2.6.0 Gerd Knorr
2004-01-16  2:33     ` Jeff Dike
2004-01-16 10:03       ` M A Young
2004-01-16 11:42         ` Gerd Knorr
2004-01-17 16:10           ` BlaisorBlade
2004-01-16 17:27         ` Jeff Dike
2004-01-16 21:56           ` Gerd Knorr
2004-01-17 21:12           ` M A Young
2004-01-18  4:47             ` Jeff Dike
2004-01-16 23:47       ` Sven Köhler
2004-01-17 19:09       ` BlaisorBlade
2004-01-17 19:50         ` Jeff Dike
2004-01-17 20:03           ` BlaisorBlade
2004-01-18  4:51             ` Jeff Dike
2004-01-18 16:21       ` Ingo Molnar
2004-01-18 21:06         ` [uml-devel] uml 2.6.1 kbuild simplifications Ingo Molnar
2004-01-19  0:08           ` [uml-devel] " Jeff Dike
2004-01-19  7:34             ` Ingo Molnar
2004-01-20 17:40               ` Jeff Dike
2004-01-18 23:57         ` [uml-devel] Re: uml-patch-2.6.0 Jeff Dike
2004-01-19  7:53           ` Ingo Molnar
2004-01-19  8:28             ` Ingo Molnar [this message]
2004-01-20  0:19               ` M A Young
2004-01-20  0:23                 ` Ingo Molnar
2004-01-20  0:41                   ` M A Young
2004-01-23 21:52                   ` [uml-devel] tt mode tls/glibc crash with 2.6 (Was: Re: uml-patch-2.6.0) M A Young
2004-01-23 23:52                     ` [uml-devel] " M A Young
2004-01-24 12:25                       ` M A Young
2004-01-24 18:20                         ` Jeff Dike
2004-01-24 19:31                           ` M A Young
2004-01-28 11:35                             ` Ingo Molnar
2004-02-05 12:30                             ` Ingo Molnar
2004-02-05 12:45                               ` M A Young
2004-02-05 13:13                                 ` Ingo Molnar
2004-02-05 13:28                                   ` M A Young
2004-02-05 18:36                                 ` Ingo Molnar
2004-02-05 19:15                                   ` M A Young
2004-02-05 19:22                                     ` Ingo Molnar
2004-02-05 19:15                                   ` Ingo Molnar
2004-02-05 19:50                                     ` Ingo Molnar
2004-02-06  7:42                                       ` Ingo Molnar
2004-01-20  1:27                 ` [uml-devel] Re: uml-patch-2.6.0 Jeff Dike
2004-01-20 17:22               ` Jeff Dike
2004-01-20 19:59                 ` Ingo Molnar
2004-01-17 19:09 ` [uml-devel] uml-patch-2.6.0 BlaisorBlade
2004-01-17 19:51   ` Jeff Dike
2004-01-18 13:49     ` Ingo Molnar
2004-01-18 13:58       ` [uml-devel] uml-patch-2.6.1-1: VFS: Cannot open root device "ubd0" or unknown-block(0, 0) Ingo Molnar
2004-01-18 14:04         ` [uml-devel] " Ingo Molnar
2004-01-18 23:48           ` Jeff Dike
2004-01-17 20:32   ` [uml-devel] uml-patch-2.6.0 M A Young
2004-01-19 17:06   ` [uml-devel] uml-patch-2.6.0 Gerd Knorr
2004-01-20 19:42     ` BlaisorBlade
2004-01-20 21:30       ` Gerd Knorr
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18 18:46 M A Young

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=20040119082805.GA4412@elte.hu \
    --to=mingo@elte.hu \
    --cc=jdike@addtoit.com \
    --cc=kraxel@bytesex.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 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.