public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@melbourne.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] XFS / IA64 system call conflict
Date: Mon, 23 Jul 2001 14:16:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005870@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005867@msgid-missing>

On Mon, 23 Jul 2001 15:53:06 +0200 (CEST), 
Martin Wilck <Martin.Wilck@fujitsu-siemens.com> wrote:
>David's last patch assigns the system call number 1215 to "getunwind".
>The XFS kernel patch for 2.4.5 vuses 1215-1217 for address control lists.
>How should this conflict be resolved? For now, I have just made XFS use
>1216-1218 instead.

The XFS syscalls for IA64 are now
        data8 sys_attrctl                       // 1260
        data8 sys_acl_get
        data8 sys_acl_set
with corresponding changes to include/asm-ia64/unistd.h.

I did some SGI internal patches for XFS+KDB against IA64 a few weeks
ago.  The problem is that IA64 is stuck on kernel 2.4.5 while XFS
development is up to 2.4.7.  There were changes to common kernel code
between 2.4.5 and 2.4.7 that affected fs handling so we cannot backport
the current XFS to the 2.4.5 IA64 kernel.  Instead I used a snapshot of
XFS as of 2.4.5, which means it is missing some bug fixes.  We would
really like a current IA64 kernel.



  parent reply	other threads:[~2001-07-23 14:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23 13:53 [Linux-ia64] XFS / IA64 system call conflict Martin Wilck
2001-07-23 14:07 ` Nathan Straz
2001-07-23 14:09 ` Jes Sorensen
2001-07-23 14:16 ` Keith Owens [this message]
2001-07-23 14:24 ` Keith Owens
2001-07-23 16:49 ` David Mosberger
2001-07-23 18:51 ` David Mosberger
2001-07-24  0:16 ` Keith Owens
2001-07-24  0:19 ` David Mosberger
2001-07-24  0:30 ` Keith Owens
2001-07-24  0:35 ` David Mosberger
2001-07-24  1:04 ` Keith Owens
2001-07-25 15:45 ` Jes Sorensen

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=marc-linux-ia64-105590693005870@msgid-missing \
    --to=kaos@melbourne.sgi.com \
    --cc=linux-ia64@vger.kernel.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