public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Paul Larson <plars@linuxtestproject.org>
Cc: Andi Kleen <ak@suse.de>, Robert Williamson <robbiew@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	aniruddha.marathe@wipro.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Re: Same syscall is defined to different numbers on 3 different archs(was Re: Makefile  issue)
Date: Tue, 8 Apr 2003 16:47:18 -0300	[thread overview]
Message-ID: <20030408164718.F18709@almesberger.net> (raw)
In-Reply-To: <1049808651.30732.113.camel@plars>; from plars@linuxtestproject.org on Tue, Apr 08, 2003 at 08:30:50AM -0500

Paul Larson wrote:
> I don't think so.  Apps should be accessing things through libraries
> anyway.  The only reason we don't in some cases like this is that it's
> new and not in libs on any distro yet.

Well yes, if the syscall is correctly implemented in the library,
there's no problem.

> Besides, I don't think having a
> /proc/syscalls would be any better than having to do ifdefs or use
> kernel headers.

#ifdef may be hard pressed to identify a specific kernel with a
specific patch. Kernel headers are obviously a solution (although
this violates the "user space must never include kernel headers"
pseudo-rule), but add the problem of needing to identify the
"current" source tree, which is a configuration step almost always
requiring manual intervention.

My suggestion for /proc/syscalls isn't entirely serious, but it 
would be nice if we could eventually solve this problem ...

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

      reply	other threads:[~2003-04-08 19:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF51DE965A.FDCB6DBE-ON85256D01.005201B1-86256D01.005610CF@pok.ibm.com.suse.lists.linux.kernel>
2003-04-07 15:54 ` Same syscall is defined to different numbers on 3 different archs(was Re: Makefile issue) Andi Kleen
2003-04-07 16:26   ` Robert Williamson
2003-04-07 18:08     ` David Mosberger
2003-04-07 18:16       ` Robert Williamson
2003-04-07 18:49         ` David Mosberger
2003-04-08  2:23   ` Werner Almesberger
2003-04-08 13:30     ` [LTP] " Paul Larson
2003-04-08 19:47       ` Werner Almesberger [this message]

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=20030408164718.F18709@almesberger.net \
    --to=wa@almesberger.net \
    --cc=ak@suse.de \
    --cc=aniruddha.marathe@wipro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=plars@linuxtestproject.org \
    --cc=robbiew@us.ibm.com \
    /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