From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] x86_64: fix 2.6.18 regression - PTRACE_OLDSETOPTIONS should be accepted
Date: Fri, 16 Feb 2007 14:02:04 -0500 [thread overview]
Message-ID: <20070216190204.GB7481@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200702152005.56594.blaisorblade@yahoo.it>
On Thu, Feb 15, 2007 at 08:05:56PM +0100, Blaisorblade wrote:
> Jeff, I verified my patch is _almost_ enough for 2.6.18 for fully booting a
> 32bit UML; on 2.6.18 I had to also add PTRACE_GET/SET_THREAD_AREA (this fix
> was merged in 2.6.19) to avoid tons of TLS errors.
I'm not seeing that. With the current set of patches, I have 32-bit UMLs
happily booting on x86_64.
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
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] x86_64: fix 2.6.18 regression - PTRACE_OLDSETOPTIONS should be accepted
Date: Fri, 16 Feb 2007 14:02:04 -0500 [thread overview]
Message-ID: <20070216190204.GB7481@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200702152005.56594.blaisorblade@yahoo.it>
On Thu, Feb 15, 2007 at 08:05:56PM +0100, Blaisorblade wrote:
> Jeff, I verified my patch is _almost_ enough for 2.6.18 for fully booting a
> 32bit UML; on 2.6.18 I had to also add PTRACE_GET/SET_THREAD_AREA (this fix
> was merged in 2.6.19) to avoid tons of TLS errors.
I'm not seeing that. With the current set of patches, I have 32-bit UMLs
happily booting on x86_64.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2007-02-16 19:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 2:34 [uml-devel] x86_64: fix 2.6.18 regression - PTRACE_OLDSETOPTIONS should be accepted Paolo 'Blaisorblade' Giarrusso
2007-02-15 2:34 ` Paolo 'Blaisorblade' Giarrusso
2007-02-15 2:54 ` [uml-devel] " Jeff Dike
2007-02-15 2:54 ` Jeff Dike
2007-02-15 3:43 ` [uml-devel] " Blaisorblade
2007-02-15 3:43 ` Blaisorblade
2007-02-15 5:51 ` Andrew Morton
2007-02-15 5:51 ` Andrew Morton
2007-02-15 17:01 ` Jeff Dike
2007-02-15 17:01 ` Jeff Dike
2007-02-15 19:05 ` Blaisorblade
2007-02-15 19:05 ` Blaisorblade
2007-02-16 19:02 ` Jeff Dike [this message]
2007-02-16 19:02 ` Jeff Dike
2007-02-17 0:04 ` Blaisorblade
2007-02-17 0:04 ` Blaisorblade
2007-02-17 0:38 ` Jeff Dike
2007-02-17 0:38 ` 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=20070216190204.GB7481@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=linux-kernel@vger.kernel.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.