From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: akpm@osdl.org, wstearns@pobox.com,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 2/3] UML - x86_64 thread fixes
Date: Thu, 22 Feb 2007 11:54:09 -0500 [thread overview]
Message-ID: <20070222165409.GC3396@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200702220107.30766.blaisorblade@yahoo.it>
On Thu, Feb 22, 2007 at 01:07:30AM +0100, Blaisorblade wrote:
> Is there any reason for avoiding this treatment to %gs, apart that TLS code
> usually does not need it, even if the API allows for it to exist?
Is there any prospect that %gs will be getting similar treatment? %fs is
set through CLONE_SETTLS, so it would seem that something like a new
clone flag would be required for this.
> I _do_
> believe this patch fixes bug which can be tested (not verified everything),
> even if I wonder why you didn't look at the patch I sent to you time ago (I
> hadn't finished it, in truth, but there was most stuff - it had problems I
> couldn't debug at that time).
Maybe because I forgot about it - do you have a pointer?
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2007-02-22 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 21:57 [uml-devel] [PATCH 2/3] UML - x86_64 thread fixes Jeff Dike
2007-02-22 0:07 ` Blaisorblade
2007-02-22 16:54 ` Jeff Dike [this message]
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=20070222165409.GC3396@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=linux-kernel@vger.kernel.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