* uapi __NR_syscalls for microblaze
@ 2013-01-03 12:59 Michal Simek
2013-01-03 14:03 ` David Howells
0 siblings, 1 reply; 6+ messages in thread
From: Michal Simek @ 2013-01-03 12:59 UTC (permalink / raw)
To: David Howells, LKML, Arnd Bergmann, Benjamin Herrenschmidt
Hi David,
just want to check with you if __NR_syscalls is necessary for user
space. I see that powerpc and arm
have this macro in asm not in uapi like Microblaze.
If is not needed by user space, I should move it to asm/unistd.h
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: uapi __NR_syscalls for microblaze
2013-01-03 12:59 uapi __NR_syscalls for microblaze Michal Simek
@ 2013-01-03 14:03 ` David Howells
2013-01-03 14:06 ` Michal Simek
0 siblings, 1 reply; 6+ messages in thread
From: David Howells @ 2013-01-03 14:03 UTC (permalink / raw)
To: Michal Simek; +Cc: dhowells, LKML, Arnd Bergmann, Benjamin Herrenschmidt
Michal Simek <monstr@monstr.eu> wrote:
> just want to check with you if __NR_syscalls is necessary for user space. I
> see that powerpc and arm have this macro in asm not in uapi like Microblaze.
> If is not needed by user space, I should move it to asm/unistd.h
It isn't as far as I know... I recommend putting your question on the
linux-arch mailing list.
David
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: uapi __NR_syscalls for microblaze
2013-01-03 14:03 ` David Howells
@ 2013-01-03 14:06 ` Michal Simek
2013-01-03 16:01 ` Arnd Bergmann
0 siblings, 1 reply; 6+ messages in thread
From: Michal Simek @ 2013-01-03 14:06 UTC (permalink / raw)
To: David Howells; +Cc: LKML, Arnd Bergmann, Benjamin Herrenschmidt, linux-arch
2013/1/3 David Howells <dhowells@redhat.com>:
> Michal Simek <monstr@monstr.eu> wrote:
>
>> just want to check with you if __NR_syscalls is necessary for user space. I
>> see that powerpc and arm have this macro in asm not in uapi like Microblaze.
>> If is not needed by user space, I should move it to asm/unistd.h
>
> It isn't as far as I know... I recommend putting your question on the
> linux-arch mailing list.
I have add linux-arch to CC.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: uapi __NR_syscalls for microblaze
2013-01-03 14:06 ` Michal Simek
@ 2013-01-03 16:01 ` Arnd Bergmann
2013-01-03 20:13 ` Michal Simek
0 siblings, 1 reply; 6+ messages in thread
From: Arnd Bergmann @ 2013-01-03 16:01 UTC (permalink / raw)
To: Michal Simek; +Cc: David Howells, LKML, Benjamin Herrenschmidt, linux-arch
On Thursday 03 January 2013, Michal Simek wrote:
> 2013/1/3 David Howells <dhowells@redhat.com>:
> > Michal Simek <monstr@monstr.eu> wrote:
> >
> >> just want to check with you if __NR_syscalls is necessary for user space. I
> >> see that powerpc and arm have this macro in asm not in uapi like Microblaze.
> >> If is not needed by user space, I should move it to asm/unistd.h
> >
> > It isn't as far as I know... I recommend putting your question on the
> > linux-arch mailing list.
>
> I have add linux-arch to CC.
Right, I'm pretty sure it's not needed, but it has traditionally been
exported on a lot of platforms, so you can keep it in UAPI to be
on the safe side.
Arnd
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: uapi __NR_syscalls for microblaze
2013-01-03 16:01 ` Arnd Bergmann
@ 2013-01-03 20:13 ` Michal Simek
2013-01-03 22:27 ` Arnd Bergmann
0 siblings, 1 reply; 6+ messages in thread
From: Michal Simek @ 2013-01-03 20:13 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: David Howells, LKML, Benjamin Herrenschmidt, linux-arch
2013/1/3 Arnd Bergmann <arnd@arndb.de>:
> On Thursday 03 January 2013, Michal Simek wrote:
>> 2013/1/3 David Howells <dhowells@redhat.com>:
>> > Michal Simek <monstr@monstr.eu> wrote:
>> >
>> >> just want to check with you if __NR_syscalls is necessary for user space. I
>> >> see that powerpc and arm have this macro in asm not in uapi like Microblaze.
>> >> If is not needed by user space, I should move it to asm/unistd.h
>> >
>> > It isn't as far as I know... I recommend putting your question on the
>> > linux-arch mailing list.
>>
>> I have add linux-arch to CC.
>
> Right, I'm pretty sure it's not needed, but it has traditionally been
> exported on a lot of platforms, so you can keep it in UAPI to be
> on the safe side.
Isn't it better to be consistent across all architectures?
If it is wrong to exported and there is no reason to use it in userspace
then all architecture should move it out of uapi.
If there is any reason then it is should be in uapi.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: uapi __NR_syscalls for microblaze
2013-01-03 20:13 ` Michal Simek
@ 2013-01-03 22:27 ` Arnd Bergmann
0 siblings, 0 replies; 6+ messages in thread
From: Arnd Bergmann @ 2013-01-03 22:27 UTC (permalink / raw)
To: Michal Simek; +Cc: David Howells, LKML, Benjamin Herrenschmidt, linux-arch
On Thursday 03 January 2013, Michal Simek wrote:
>
> 2013/1/3 Arnd Bergmann <arnd@arndb.de>:
> > On Thursday 03 January 2013, Michal Simek wrote:
> >> 2013/1/3 David Howells <dhowells@redhat.com>:
> >> > Michal Simek <monstr@monstr.eu> wrote:
> >> >
> >> >> just want to check with you if __NR_syscalls is necessary for user space. I
> >> >> see that powerpc and arm have this macro in asm not in uapi like Microblaze.
> >> >> If is not needed by user space, I should move it to asm/unistd.h
> >> >
> >> > It isn't as far as I know... I recommend putting your question on the
> >> > linux-arch mailing list.
> >>
> >> I have add linux-arch to CC.
> >
> > Right, I'm pretty sure it's not needed, but it has traditionally been
> > exported on a lot of platforms, so you can keep it in UAPI to be
> > on the safe side.
>
> Isn't it better to be consistent across all architectures?
Yes, certainly.
> If it is wrong to exported and there is no reason to use it in userspace
> then all architecture should move it out of uapi.
> If there is any reason then it is should be in uapi.
I don't really care which way we do it, I think you can rightfully argue
either way. AFAICT x86 doesn't even define __NR_syscalls at all, so
it's clearly not part of the ABI.
Arnd
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-01-03 22:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-03 12:59 uapi __NR_syscalls for microblaze Michal Simek
2013-01-03 14:03 ` David Howells
2013-01-03 14:06 ` Michal Simek
2013-01-03 16:01 ` Arnd Bergmann
2013-01-03 20:13 ` Michal Simek
2013-01-03 22:27 ` Arnd Bergmann
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.