From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Chris Wedgwood <cw@f00f.org>, William Stearns <wstearns@pobox.com>
Subject: Re: [uml-devel] glibc and NPTL, problem, workarounds, etc.
Date: Sun, 12 Sep 2004 21:27:12 +0200 [thread overview]
Message-ID: <200409122127.12738.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040912190258.GA7818@taniwha.stupidest.org>
On Sunday 12 September 2004 21:02, Chris Wedgwood wrote:
> On Sun, Sep 12, 2004 at 08:20:51PM +0200, BlaisorBlade wrote:
> > There is another patch which should make the work - (I never tested
> > it, but it should work). Basically, uname will state it is a "i586"
> > rather than "i686",
> > so NPTL is not enabled:
> > http://www.suse.de/~kraxel/uml/patches/uml-pretend-to-be-i586
> This apparently only works because people[1] ship either i386 or i686
> libc and only the latter has NPTL support --- but there is nothing
> preventing i586 NPTL support in the future...
Are you sure? I remember that NPTL needs using some new instructions of i686
(maybe CMOVxx) for futexes, to be atomic.
However, if I'm wrong, we could even pretend to be i386.
> --cw
> [1] RH & Debian checked, maybe this isn't true for gentoo in which
> case it will break there?
Well, you compile Gentoo for your own processor - you might maybe even enable
-mregparm for everything (which even breaks binary compatibility everything).
I guess if you build Gentoo on an i386, it will either refuse to build or
build an i386 glibc. Otherwise, it does not make sense for them to ship i386
glibc.
That said, you must just be careful when building the guest root_fs, with
Gentoo.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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:[~2004-09-12 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 19:02 [uml-devel] glibc and NPTL, problem, workarounds, etc William Stearns
2004-09-08 20:08 ` Steven Pritchard
2004-09-12 18:20 ` BlaisorBlade
2004-09-12 19:02 ` Chris Wedgwood
2004-09-12 19:27 ` BlaisorBlade [this message]
2004-09-12 19:32 ` Chris Wedgwood
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=200409122127.12738.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=cw@f00f.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=wstearns@pobox.com \
/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