linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org, rmk@arm.linux.org.uk, sam@ravnborg.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH] Complain about missing system calls.
Date: Fri, 9 Mar 2007 20:35:24 +0100	[thread overview]
Message-ID: <20070309193524.GX18564@lug-owl.de> (raw)
In-Reply-To: <20070309190051.GA20521@one.firstfloor.org>

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

On Fri, 2007-03-09 20:00:51 +0100, Andi Kleen <andi@firstfloor.org> wrote:
> > Not everybody has a simple indexed list of pointers :)  For example,
> > for vax-linux, we use a struct per syscall with the expected number of
> > on-stack longwords for the call.
> > 
> > So if something "new" is coming up, please keep in mind that it should
> > be flexible enough to represent that. :)
> 
> Are there plans to merge vax any time soon to mainline? 

Well...  That depends :)  For now, I'd prefer to stay out of mainline,
until we're having gcc-trunk with a current GNU libc up'n'running.
Until then, I plan to at least break the complete ABI once (drop old
syscals and _only_ wire up their modern counterparts.)

> Normally we don't care very much about out of tree code, especially
> if it adds complexity like this.

Sure, but at least mentioning that there's more than only a simple
table of function pointers may or may not help to *plan* the code to
fit future needs.

> But I suspect s390 would need number of arguments anyways.

Any they're already merged. Yay :)

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
  Signature of:                           Wenn ich wach bin, träume ich.
  the second  :

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-03-09 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1173394873.3461.510.camel@pmac.infradead.org>
2007-03-09 16:11 ` [PATCH] Complain about missing system calls Andi Kleen
2007-03-09 16:38   ` Jan-Benedict Glaw
2007-03-09 19:00     ` Andi Kleen
2007-03-09 19:35       ` Jan-Benedict Glaw [this message]
2007-03-10  9:58       ` Martin Schwidefsky
2007-03-09 19:40     ` H. Peter Anvin
2007-03-09 20:13       ` Russell King
2007-03-09 20:52         ` H. Peter Anvin
2007-03-09 16:47   ` Benjamin Herrenschmidt
2007-03-09 18:54     ` Andi Kleen
2007-03-10  9:51       ` Martin Schwidefsky
2007-03-09 17:20   ` David Woodhouse

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=20070309193524.GX18564@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=akpm@osdl.org \
    --cc=andi@firstfloor.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).