From: Nicholas Miell <nmiell@comcast.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Ulrich Drepper <drepper@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] prototypes for *at functions & typo fix
Date: Wed, 18 Jan 2006 20:56:26 -0800 [thread overview]
Message-ID: <1137646586.2842.6.camel@entropy> (raw)
In-Reply-To: <20060118203733.5aac5ee4.akpm@osdl.org>
On Wed, 2006-01-18 at 20:37 -0800, Andrew Morton wrote:
> Ulrich Drepper <drepper@redhat.com> wrote:
> >
> > Do we really need the __NR_ia32_* macros? The userlevel on x86-64 should be bi-arch and provide the native ia32 unistd.h.
>
> I'd have thought that x86 and x86_64 could source-level-share the syscall
> table, yes. ppc manages to.
AMD64 renumbered all the syscalls for optimal cacheline usage or
something stupid like that. I suppose the x86 emulation on AMD64 kernels
could share the i386 table, but then _NR_foo will have a different value
depending on context, and that'll just get confusing.
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2006-01-19 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 4:29 [PATCH] prototypes for *at functions & typo fix Ulrich Drepper
2006-01-19 4:37 ` Andrew Morton
2006-01-19 4:56 ` Nicholas Miell [this message]
2006-01-19 6:07 ` Ulrich Drepper
2006-01-19 6:37 ` Nicholas Miell
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=1137646586.2842.6.camel@entropy \
--to=nmiell@comcast.net \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.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.