linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu
Subject: Re: uml doesn't work on 2.6.24-rc2
Date: Wed, 14 Nov 2007 09:22:47 -0500	[thread overview]
Message-ID: <20071114142247.GA5848@c2.user-mode-linux.org> (raw)
In-Reply-To: <E1IsFbA-0007y2-00@dorka.pomaz.szeredi.hu>

On Wed, Nov 14, 2007 at 11:35:56AM +0100, Miklos Szeredi wrote:
> Note, this is 32bit UML on 64bit host, to complicate matters.  So I
> think it's not PTRACE_ARCH_PRCTL, but PTRACE_SET_THREAD_AREA.

Oh, that changes things.  In this case, I believe this problem is fixed
by fd181c72a3c202a3986bcee7551c0838265aec2a.

You'll also need f86f9e6d66027bdcdc9b40c06d431ee53ea0d509 for a
separate problem.

> Maybe this is a fallout from the x86 architecture merge?

No, the problems had been there from before the merge - years, in the
case of the second one.

				Jeff

-- 
Work email - jdike at linux dot intel dot com

  reply	other threads:[~2007-11-14 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 23:32 uml doesn't work on 2.6.24-rc2 Miklos Szeredi
2007-11-14  1:10 ` Jeff Dike
2007-11-14 10:35   ` Miklos Szeredi
2007-11-14 14:22     ` Jeff Dike [this message]
2007-11-14 15:26       ` Miklos Szeredi
2007-11-14 17:36         ` Jeff Dike
2007-11-14 21:29           ` Miklos Szeredi
2007-11-16 17:06             ` Jeff Dike
2007-11-22 18:08               ` Miklos Szeredi
2007-11-22 23:51                 ` Jeff Dike
2007-11-23  8:59                   ` Miklos Szeredi
2007-11-23  9:01                   ` [uml-devel] " Karol Swietlicki
2007-11-23 10:54                     ` Jiri Olsa
2007-11-23 11:00                       ` WANG Cong
2007-11-26 17:47             ` Jeff Dike
2007-11-26 18:10             ` Jeff Dike
2007-11-26 20:52         ` Jeff Dike
2007-11-26 21:22           ` Miklos Szeredi

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=20071114142247.GA5848@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).