From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 3/5] UML - Clean up tt mode remapping of UML binary
Date: Tue, 7 Jun 2005 00:53:21 +0100 [thread overview]
Message-ID: <20050606235321.GJ29811@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200506070105.20422.blaisorblade@yahoo.it>
On Tue, Jun 07, 2005 at 01:05:19AM +0200, Blaisorblade wrote:
> On Monday 06 June 2005 22:08, Jeff Dike wrote:
> > From Al Viro - this turns the tt mode remapping of the binary into arch
> > code.
> NACK at all, definitely, don't apply this one please. This patch:
>
> 1) On i386 does not fix the problem it was supposed to fix when I originately
> sent the first version (i.e. avoiding to create a .thread_private section to
> allow linking against NPTL glibc). It's done on x86_64 and forgot on i386.
True. i386 still assumes non-NPTL (as it is on the box I'm working on -
such setups *do* exist).
> 2) Splitting the linker script for subarchs is definitely not needed.
Per-subarch - perhaps not. Per-glibc-type - definitely needed.
> 3) This removes the fix (done through objcopy -G switcheroo) to a link time
> conflict happening on some weird glibc combinations.
*What* link-time conflict? We don't link libc into switcheroo anymore.
next prev parent reply other threads:[~2005-06-07 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 20:08 Jeff Dike
2005-06-06 23:05 ` [uml-devel] " Blaisorblade
2005-06-06 23:53 ` Al Viro [this message]
2005-06-07 0:56 ` Blaisorblade
2005-06-07 0:59 ` Al Viro
2005-06-07 1:18 ` Blaisorblade
2005-06-07 3:46 ` Rob Landley
2005-06-07 2:00 ` Jeff Dike
2005-06-07 0:40 ` Jeff Dike
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=20050606235321.GJ29811@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®