public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: sys_tux stolen @s390 in 2.6
@ 2004-02-19  9:30 Arnd Bergmann
  0 siblings, 0 replies; 4+ messages in thread
From: Arnd Bergmann @ 2004-02-19  9:30 UTC (permalink / raw)
  To: Pete Zaitcev; +Cc: Martin Schwidefsky, linux-kernel

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


^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: sys_tux stolen @s390 in 2.6
@ 2004-02-19  9:56 Martin Schwidefsky
  0 siblings, 0 replies; 4+ messages in thread
From: Martin Schwidefsky @ 2004-02-19  9:56 UTC (permalink / raw)
  To: Arnd Bergmann; +Cc: linux-kernel, Pete Zaitcev






Hi Arnd,

> 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).

Ahh, this explains it. I was already worried that I have misplaced
some mail that reserved #222 for tux. The official number is indeed
#242.

blue skies,
   Martin

Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com



^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: sys_tux stolen @s390 in 2.6
@ 2004-02-19  8:53 Martin Schwidefsky
  0 siblings, 0 replies; 4+ messages in thread
From: Martin Schwidefsky @ 2004-02-19  8:53 UTC (permalink / raw)
  To: Pete Zaitcev; +Cc: linux-kernel, mingo, zaitcev






Hi Pete,

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

Did we? In my copy of 2.4 #222 is sys_readahead as well. I checked all
version of unistd in our cvs and there isn't a trace of sys_tux. It would
be really bad to have version of tux out there using a system call number
that is used for something different. Who reserved the number?

blue skies,
   Martin

Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com



^ permalink raw reply	[flat|nested] 4+ messages in thread
* sys_tux stolen @s390 in 2.6
@ 2004-02-19  0:52 Pete Zaitcev
  0 siblings, 0 replies; 4+ messages in thread
From: Pete Zaitcev @ 2004-02-19  0:52 UTC (permalink / raw)
  To: schwidefsky; +Cc: mingo, zaitcev, linux-kernel

Hi, Martin -

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

Thanks,
-- Pete

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-02-19  9:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-19  9:30 sys_tux stolen @s390 in 2.6 Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2004-02-19  9:56 Martin Schwidefsky
2004-02-19  8:53 Martin Schwidefsky
2004-02-19  0:52 Pete Zaitcev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox