lkml.org 
[lkml]   [2004]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: sys_tux stolen @s390 in 2.6
Date
Pete wrote:

> in 2.4, syscall #222 was reserved for tux on s390, but now it is used
> by sys_readahead. What do we do now?

In my copy of tux-3.2.13, the number 242 is used correctly. That number
is the one that is reserved in the official linux sources. Martin
allocated it exactly one year ago when I sent the patch enabling
s390 in tux to Florian La Roche <laroche@redhat.com>.

If you have a really old version of the tux sources, there might
be the fallback to number 222 still there (which is a pretty dumb
idea, btw).

Arnd <><

from tux.c:
#if defined(__powerpc__)
#define __NR_tux 225
#elif defined(__x86_64__)
#define __NR_tux 184
#elif defined(__alpha__)
#define __NR_tux 397
#elif defined(__s390__)
#define __NR_tux 242
#elif (defined (__i386__) || defined (__arm__))
#define __NR_tux 222
#else
#warning unsupported architecture, guessing __NR_tux=222 like x86...
#define __NR_tux 222
#endif

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:01    [W:0.038 / U:0.656 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site