public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Chris Wright <chrisw@osdl.org>
Cc: blaisorblade@yahoo.it, akpm@osdl.org,
	bstroesser@fujitsu-siemens.com, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [patch 1/7] uml: fix syscall table by including $(SUBARCH)'s one, for i386
Date: Thu, 28 Apr 2005 16:48:58 -0400	[thread overview]
Message-ID: <20050428204858.GD25451@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20050428181053.GQ23013@shell0.pdx.osdl.net>

On Thu, Apr 28, 2005 at 11:10:53AM -0700, Chris Wright wrote:
> * blaisorblade@yahoo.it (blaisorblade@yahoo.it) wrote:
> > 
> > Split the i386 entry.S files into entry.S and syscall_table.S which
> > is included in the previous one (so actually there is no difference between
> > them) and use the syscall_table.S in the UML build, instead of tracking by
> > hand the syscall table changes (which is inherently error-prone).
> 
> Xen can use this as well (it was on my todo list).

Maybe talking out of my ass here, but would it make sense to have the
generic syscalls in asm-generic, in the form of something like:
	SYSCALL(__NR_getpid, sys_getpid)
?

The arch include this into its syscall table, would continue to define
__NR_*, and it would define SYSCALL (but all the syscall tables I've
seen are just arrays of pointers).  This would allow the arches to
automatically get all the generic system calls, and they'd continue to
define on their own any arch-specific things.

				Jeff

  reply	other threads:[~2005-04-28 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24 18:19 [patch 1/7] uml: fix syscall table by including $(SUBARCH)'s one, for i386 blaisorblade
2005-04-26 11:33 ` Andrew Morton
2005-04-29 19:10   ` Blaisorblade
2005-04-28 18:10 ` Chris Wright
2005-04-28 20:48   ` Jeff Dike [this message]
2005-05-01 11:15     ` Factoring out common syscalls into asm-generic (was: Re: [uml-devel] " Blaisorblade
2005-04-29 20:31   ` Blaisorblade

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=20050428204858.GD25451@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=chrisw@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox