public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Nicholas Miell <nmiell@comcast.net>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] prototypes for *at functions & typo fix
Date: Wed, 18 Jan 2006 22:07:31 -0800	[thread overview]
Message-ID: <43CF2CA3.5020001@redhat.com> (raw)
In-Reply-To: <1137646586.2842.6.camel@entropy>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Nicholas Miell wrote:
> 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.

Yes, the syscall numbers are quite different, especially because x86 has
all syscalls, even the obsolete ones.

But what I mean is that the __NR_ia32_* macros in
asm-x86-64/ia32_unistd.h aren't used anywhere in the kernel.  And in
userland the asm-x86/unistd.h file is used when compiling x86 apps.  At
least this is how the kernel headers for userlevel use should be set up.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2006-01-19  6:06 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
2006-01-19  6:07     ` Ulrich Drepper [this message]
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=43CF2CA3.5020001@redhat.com \
    --to=drepper@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nmiell@comcast.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