From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Jeff Dike <jdike@addtoit.com>,
"Paolo 'Blaisorblade' Giarrusso" <blaisorblade@yahoo.it>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/9] Shared ia32 syscall table
Date: Tue, 24 Jan 2006 10:02:42 +0100 [thread overview]
Message-ID: <200601241002.43408.ak@suse.de> (raw)
In-Reply-To: <200601240355_MC3-1-B687-9FD3@compuserve.com>
On Tuesday 24 January 2006 09:53, Chuck Ebbert wrote:
> In-Reply-To: <200601240141.08152.ak@suse.de>
>
> On Tue, 24 Jan 2006 at 01:41:07 +0100, Andi Kleen wrote:
>
> > On Tuesday 24 January 2006 01:36, Chuck Ebbert wrote:
> > > This patch series updates i386 and x86_64 so they share
> > > the same ia32 syscall table. UML already uses the i386
> > > table and is updated to use the new shared table as well.
> >
> > That's wrong for x86-64. The IA32 syscall table needs
> > to point to compat_* version of syscalls, while the native
> > IA32 table uses sys_* directly.
>
> How could I have possibly gotten a successful boot of an i386
> distro on top of the patched x86_64 kernel if this were wrong?
>
> Did you even look at the patches?
No, because they arrived more than an hour after the initial
description and i just replied to that.
Looking at the patch I must say I prefer the old straight
table over your #define mess.
-Andi
next prev parent reply other threads:[~2006-01-24 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 8:53 [patch 0/9] Shared ia32 syscall table Chuck Ebbert
2006-01-24 9:02 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-24 0:36 Chuck Ebbert
2006-01-24 0:41 ` Andi Kleen
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=200601241002.43408.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.