Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1223943 > unrolled thread

[PATCH v2 0/4] m68k: System call updates

Started byGeert Uytterhoeven <geert@linux-m68k.org>
First post2015-09-14 11:00 +0200
Last post2015-09-17 17:50 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.kernel

Contents

  [PATCH v2 0/4] m68k: System call updates Geert Uytterhoeven <geert@linux-m68k.org> - 2015-09-14 11:00 +0200
    Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls Andreas Schwab <schwab@linux-m68k.org> - 2015-09-17 16:40 +0200
      Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls Geert Uytterhoeven <geert@linux-m68k.org> - 2015-09-17 17:20 +0200
        Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls Andreas Schwab <schwab@linux-m68k.org> - 2015-09-17 17:50 +0200

#1223943 — [PATCH v2 0/4] m68k: System call updates

FromGeert Uytterhoeven <geert@linux-m68k.org>
Date2015-09-14 11:00 +0200
Subject[PATCH v2 0/4] m68k: System call updates
Message-ID<q8xMe-1gc-7@gated-at.bofh.it>
	Hi,

This patch series, intended for v4.3, updates the m68k system calls:
  - Wire up direct socket and ipc calls,
  - Wire up new userfaultfd and membarrier system calls.

Changes compared to v1:
  - Add missing recvmmsg and sendmmsg,
  - Renumbered userfaultfd,
  - New patches 3 and 4.

Geert Uytterhoeven (4):
  m68k: Wire up direct socket calls
  m68k: Wire up userfaultfd
  m68k: Wire up direct ipc calls
  m68k: Wire up membarrier

 arch/m68k/include/asm/unistd.h      |  2 +-
 arch/m68k/include/uapi/asm/unistd.h | 30 ++++++++++++++++++++++++++++++
 arch/m68k/kernel/syscalltable.S     | 31 ++++++++++++++++++++++++++++++-
 3 files changed, 61 insertions(+), 2 deletions(-)

-- 
1.9.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/

[toc] | [next] | [standalone]

#1227079 — Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls

FromAndreas Schwab <schwab@linux-m68k.org>
Date2015-09-17 16:40 +0200
SubjectRe: [PATCH v2 3/4] m68k: Wire up direct ipc calls
Message-ID<q9IvT-6qB-1@gated-at.bofh.it>
In reply to#1223943
Geert Uytterhoeven <geert@linux-m68k.org> writes:

> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> v2:
>   - New.
> ---
>  arch/m68k/include/asm/unistd.h      |  2 +-
>  arch/m68k/include/uapi/asm/unistd.h | 11 +++++++++++
>  arch/m68k/kernel/syscalltable.S     | 11 +++++++++++
>  3 files changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/arch/m68k/include/asm/unistd.h b/arch/m68k/include/asm/unistd.h
> index d25d5a5c83cb6d6b..887667ad6a2f9536 100644
> --- a/arch/m68k/include/asm/unistd.h
> +++ b/arch/m68k/include/asm/unistd.h
> @@ -4,7 +4,7 @@
>  #include <uapi/asm/unistd.h>
>  
>  
> -#define NR_syscalls		374
> +#define NR_syscalls		385
>  
>  #define __ARCH_WANT_OLD_READDIR
>  #define __ARCH_WANT_OLD_STAT
> diff --git a/arch/m68k/include/uapi/asm/unistd.h b/arch/m68k/include/uapi/asm/unistd.h
> index 0eebb28488eced36..98298206127d0930 100644
> --- a/arch/m68k/include/uapi/asm/unistd.h
> +++ b/arch/m68k/include/uapi/asm/unistd.h
> @@ -379,5 +379,16 @@
>  #define __NR_recvmmsg		371
>  #define __NR_sendmmsg		372
>  #define __NR_userfaultfd	373
> +#define __NR_msgget		374
> +#define __NR_msgctl		375
> +#define __NR_msgrcv		376
> +#define __NR_msgsnd		377
> +#define __NR_semget		378
> +#define __NR_semctl		379
> +#define __NR_semtimedop		380
> +#define __NR_shmget		381
> +#define __NR_shmctl		382
> +#define __NR_shmat		383
> +#define __NR_shmdt		384

It would be nice if the direct syscalls would drop the use of
ipc_parse_version.  Currently, apart from going through the ipc
multiplexer, the semctl, shmctl and msgctl wrappers in libc need to add
the IPC_64 bit to the cmd operand.  If that would be implied then no
special wrappers would be needed any more for direct syscalls.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
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/

[toc] | [prev] | [next] | [standalone]

#1227111 — Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls

FromGeert Uytterhoeven <geert@linux-m68k.org>
Date2015-09-17 17:20 +0200
SubjectRe: [PATCH v2 3/4] m68k: Wire up direct ipc calls
Message-ID<q9J8D-7rl-35@gated-at.bofh.it>
In reply to#1227079
Hi Andreas,

On Thu, Sep 17, 2015 at 5:09 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>> You mean that we should drop "select ARCH_WANT_IPC_PARSE_VERSION",
>> but we can't do that because an indirect call through sys_ipc() would
>> still need it when dispatching to sys_{sem,shm,msg}ctl()?
>
> Yes.  But all architectures that currently use both sys_ipc and
> ARCH_WANT_IPC_PARSE_VERSION would benefit from decoupling it when they
> add the direct syscalls.

Do we currently have architectures that use both sys_ipc and the direct
syscalls, where keeping ipc_parse_version() in the direct syscalls is required?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
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/

[toc] | [prev] | [next] | [standalone]

#1227145 — Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls

FromAndreas Schwab <schwab@linux-m68k.org>
Date2015-09-17 17:50 +0200
SubjectRe: [PATCH v2 3/4] m68k: Wire up direct ipc calls
Message-ID<q9JBE-80u-9@gated-at.bofh.it>
In reply to#1227111
Geert Uytterhoeven <geert@linux-m68k.org> writes:

> Do we currently have architectures that use both sys_ipc and the direct
> syscalls, where keeping ipc_parse_version() in the direct syscalls is required?

IMHO it doesn't make sense to suport IPC_OLD via the direct syscalls,
even for those architectures that started with them in the first place.
There are quite a few architectures that define
ARCH_WANT_IPC_PARSE_VERSION even though they started life after IPC_64
was added.  They probably just forgot to adjust ipc/util.h back then.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
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/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web