From: Herbert Poetzl <herbert@13thfloor.at>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Matthew Wilcox <willy@debian.org>,
vserver@list.linux-vserver.org, Christoph Hellwig <hch@lst.de>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [Vserver] Re: [parisc-linux] syscall number for vserver
Date: Fri, 19 Dec 2003 02:00:35 +0100 [thread overview]
Message-ID: <20031219010035.GB7469@MAIL.13thfloor.at> (raw)
In-Reply-To: <20031218195535.GA12591@colo.lackof.org>
On Thu, Dec 18, 2003 at 12:55:35PM -0700, Grant Grundler wrote:
> On Thu, Dec 18, 2003 at 05:28:09PM +0100, Herbert Poetzl wrote:
> > personally, I believe that the whole syscall number
> > allocation per architecture is broken by design,
>
> No it's definitely not.
since you removed it from the original context ...
I agree from a technical point of view, but not from
the developer's perspective (who just want's a syscall
for whatever arch independant use ...)
> Binary compatibility with other OS's is an arch specific problem.
for sure it is, but I don't see a relation there ...
> In our case, any chance of support for HPUX would
> require reserving HPUX syscall numbers and provide
> appropriate wrappers in the kernel to support it.
so where is the problem, having an additional offset/info
in the macro defining the syscall can handle that, why
has it to be a different numbering for 'linux' syscalls?
> And I don't see why the value of a syscall matters.
it doesn't matter, and it doesn't matter to me ...
> Just use the right header files and it should work on any arch.
right, but getting one syscall for every arch, seems
like a jigsaw puzzle, as the original thread shows ...
best,
Herbert
> grant
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2003-12-19 1:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 22:16 [parisc-linux] syscall number for vserver Herbert Poetzl
2003-12-18 7:25 ` Christoph Hellwig
2003-12-18 15:01 ` [Vserver] " Herbert Poetzl
2003-12-18 15:01 ` Herbert Poetzl
2003-12-18 16:04 ` Matthew Wilcox
2003-12-18 16:28 ` Herbert Poetzl
2003-12-18 19:55 ` Grant Grundler
2003-12-18 19:55 ` Grant Grundler
2003-12-19 1:00 ` Herbert Poetzl [this message]
2003-12-19 2:03 ` Grant Grundler
2003-12-19 3:24 ` Herbert Poetzl
2003-12-19 3:24 ` Herbert Poetzl
2003-12-19 16:11 ` Grant Grundler
2003-12-19 16:11 ` Grant Grundler
2003-12-19 17:03 ` Herbert Poetzl
2003-12-19 17:03 ` Herbert Poetzl
2003-12-20 1:51 ` Grant Grundler
2003-12-20 1:54 ` Herbert Poetzl
2003-12-20 1:54 ` Herbert Poetzl
2003-12-20 1:51 ` Grant Grundler
2003-12-19 2:03 ` Grant Grundler
2003-12-19 1:00 ` Herbert Poetzl
2003-12-18 16:28 ` Herbert Poetzl
2003-12-18 16:04 ` Matthew Wilcox
2003-12-18 7:25 ` Christoph Hellwig
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=20031219010035.GB7469@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=grundler@parisc-linux.org \
--cc=hch@lst.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=vserver@list.linux-vserver.org \
--cc=willy@debian.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