From: Jeff Dike <jdike@addtoit.com>
To: Paolo Giarrusso <blaisorblade@yahoo.it>
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 15:22:31 -0400 [thread overview]
Message-ID: <20060614192231.GA5325@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060613234551.69651.qmail@web25218.mail.ukl.yahoo.com>
On Wed, Jun 14, 2006 at 01:45:51AM +0200, Paolo Giarrusso wrote:
> If that problem has been fixed, this would imply that SKAS should
> work on x86-64... or not?
No, this has nothing to do with skas or ia32 emulation. It was a
straightforward register corruption bug.
Jeff
_______________________________________________
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: Paolo Giarrusso <blaisorblade@yahoo.it>
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 15:22:31 -0400 [thread overview]
Message-ID: <20060614192231.GA5325@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060613234551.69651.qmail@web25218.mail.ukl.yahoo.com>
On Wed, Jun 14, 2006 at 01:45:51AM +0200, Paolo Giarrusso wrote:
> If that problem has been fixed, this would imply that SKAS should
> work on x86-64... or not?
No, this has nothing to do with skas or ia32 emulation. It was a
straightforward register corruption bug.
Jeff
next prev parent reply other threads:[~2006-06-14 19:22 UTC|newest]
Thread overview: 30+ 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-14 18:25 ` Alberto Bertogli
2006-05-15 3:39 ` [uml-devel] " Jeff Dike
2006-05-15 3:39 ` Jeff Dike
2006-05-15 15:29 ` Alberto Bertogli
2006-05-15 15:29 ` Alberto Bertogli
2006-05-16 19:12 ` Jeff Dike
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 2:39 ` Alberto Bertogli
2006-05-17 6:36 ` Blaisorblade
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-17 18:57 ` Alberto Bertogli
2006-05-18 19:48 ` Alberto Bertogli
2006-05-18 19:48 ` Alberto Bertogli
2006-05-19 1:20 ` Blaisorblade
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:12 ` Jeff Dike
2006-05-17 18:38 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-17 18:38 ` Alberto Bertogli
2006-06-13 14:57 ` Alberto Bertogli
2006-06-13 14:57 ` Alberto Bertogli
2006-06-13 18:21 ` [uml-devel] " Jeff Dike
2006-06-13 18:21 ` Jeff Dike
2006-06-13 23:45 ` [uml-devel] " Paolo Giarrusso
2006-06-13 23:45 ` Paolo Giarrusso
2006-06-14 19:22 ` Jeff Dike [this message]
2006-06-14 19:22 ` [uml-devel] " 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=20060614192231.GA5325@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.