From: Paolo Giarrusso <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64
Date: Wed, 14 Jun 2006 01:45:51 +0200 (CEST) [thread overview]
Message-ID: <20060613234551.69651.qmail@web25218.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20060613182129.GA4619@ccure.user-mode-linux.org>
Jeff Dike <jdike@addtoit.com> ha scritto:
> On Tue, Jun 13, 2006 at 11:57:18AM -0300, Alberto Bertogli wrote:
> > I just wanted to report that this went away when trying
> 2.6.17-rc6 as a
> > host. It also works fine as a guest (after I patch it with
> >
>
http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.17-rc4/patches/jmpbuf
> > so that it builds).
> > Besides, the random segfault problems I had with previous guests
> > versions also seem to be fixed.
> These two problems are related, and were both on the host. Bodo
> Stroesser reported a while ago that ptrace, by returning via sysret
> rather than iret, could cause register corruption when tracing
> sigreturn.
> The UML crash seems to have been caused by the fix to that problem.
If that problem has been fixed, this would imply that SKAS should
work on x86-64... or not? Well, I remember that problem being on IA32
emulation and IA32 wasn't included in the patch (for what I can see).
Can you ask more information about this? Also, could you verify if at
least with noprocmm and a host SKAS-V9 it works? Two things are to
check:
* Uml64 should use /proc/mm64 (unimplemented)
* Uml64 should use the right version of PTRACE_FAULTINFO (I don't
remember what I did, if I introduced PTRACE_EX_FAULTINFO or if I
directly added the missing trap_no field in PTRACE_FAULTINFO; please
verify).
I won't have the time to check this at least until the 22 June.
Bye
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
_______________________________________________
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:[~2006-06-13 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 18:25 [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-15 3:39 ` Jeff Dike
2006-05-15 15:29 ` Alberto Bertogli
2006-05-16 19:12 ` Jeff Dike
2006-05-17 2:39 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64ync-mailbox><next-undeleted><enter-command>set editor=vim Alberto Bertogli
2006-05-17 6:36 ` Blaisorblade
2006-05-17 18:57 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-18 19:48 ` Alberto Bertogli
2006-05-19 1:20 ` Blaisorblade
2006-05-17 18:12 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64ync-mailbox><next-undeleted><enter-command>set editor=vim Jeff Dike
2006-05-17 18:38 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-06-13 14:57 ` Alberto Bertogli
2006-06-13 18:21 ` Jeff Dike
2006-06-13 23:45 ` Paolo Giarrusso [this message]
2006-06-14 19:22 ` 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=20060613234551.69651.qmail@web25218.mail.ukl.yahoo.com \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox