From: Laurent Vivier <laurent@vivier.eu>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] linux-user: Add SOCKOP_sendmmsg and SOCKOP_recvmmsg socket call, wire them up.
Date: Thu, 24 Dec 2015 22:16:41 +0100 [thread overview]
Message-ID: <567C60B9.6080208@vivier.eu> (raw)
In-Reply-To: <1450983599-6060-2-git-send-email-glaubitz@physik.fu-berlin.de>
Le 24/12/2015 19:59, John Paul Adrian Glaubitz a écrit :
> Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> ---
> linux-user/syscall.c | 8 ++++++--
> linux-user/syscall_defs.h | 2 ++
> 2 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 6c64ba6..dd6ed47 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -2171,7 +2171,6 @@ static abi_long do_sendrecvmsg(int fd, abi_ulong target_msg,
> return ret;
> }
>
> -#ifdef TARGET_NR_sendmmsg
> /* We don't rely on the C library to have sendmmsg/recvmmsg support,
> * so it might not have this *mmsg-specific flag either.
> */
> @@ -2218,7 +2217,6 @@ static abi_long do_sendrecvmmsg(int fd, abi_ulong target_msgvec,
> }
> return ret;
> }
> -#endif
>
> /* If we don't have a system accept4() then just call accept.
> * The callsites to do_accept4() will ensure that they don't
> @@ -2441,6 +2439,8 @@ static abi_long do_socketcall(int num, abi_ulong vptr)
> [SOCKOP_shutdown] = 2, /* sockfd, how */
> [SOCKOP_sendmsg] = 3, /* sockfd, msg, flags */
> [SOCKOP_recvmsg] = 3, /* sockfd, msg, flags */
> + [SOCKOP_sendmmsg] = 4, /* sockfd, msgvec, vlen, flags */
> + [SOCKOP_recvmmsg] = 4, /* sockfd, msgvec, vlen, flags */
> [SOCKOP_setsockopt] = 5, /* sockfd, level, optname, optval, optlen */
> [SOCKOP_getsockopt] = 5, /* sockfd, level, optname, optval, optlen */
> };
> @@ -2491,6 +2491,10 @@ static abi_long do_socketcall(int num, abi_ulong vptr)
> return do_sendrecvmsg(a[0], a[1], a[2], 1);
> case SOCKOP_recvmsg: /* sockfd, msg, flags */
> return do_sendrecvmsg(a[0], a[1], a[2], 0);
> + case SOCKOP_sendmmsg: /* sockfd, msgvec, vlen, flags */
> + return do_sendrecvmmsg(a[0], a[1], a[2], a[3], 1);
> + case SOCKOP_recvmmsg: /* sockfd, msgvec, vlen, flags */
> + return do_sendrecvmmsg(a[0], a[1], a[2], a[3], 0);
> case SOCKOP_setsockopt: /* sockfd, level, optname, optval, optlen */
> return do_setsockopt(a[0], a[1], a[2], a[3], a[4]);
> case SOCKOP_getsockopt: /* sockfd, level, optname, optval, optlen */
> diff --git a/linux-user/syscall_defs.h b/linux-user/syscall_defs.h
> index f996acf..0d6d141 100644
> --- a/linux-user/syscall_defs.h
> +++ b/linux-user/syscall_defs.h
> @@ -28,6 +28,8 @@
> #define SOCKOP_sendmsg 16
> #define SOCKOP_recvmsg 17
> #define SOCKOP_accept4 18
> +#define SOCKOP_recvmmsg 19
> +#define SOCKOP_sendmmsg 20
>
> #define IPCOP_semop 1
> #define IPCOP_semget 2
>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
next prev parent reply other threads:[~2015-12-24 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 18:59 [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 John Paul Adrian Glaubitz
2015-12-24 18:59 ` [Qemu-devel] [PATCH 2/2] linux-user: Add SOCKOP_sendmmsg and SOCKOP_recvmmsg socket call, wire them up John Paul Adrian Glaubitz
2015-12-24 21:16 ` Laurent Vivier [this message]
2015-12-24 19:04 ` [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 John Paul Adrian Glaubitz
2015-12-24 21:21 ` Laurent Vivier
2015-12-25 0:02 ` John Paul Adrian Glaubitz
2016-01-11 13:46 ` Riku Voipio
2016-01-11 13:54 ` Laurent Vivier
2016-01-11 13:57 ` John Paul Adrian Glaubitz
2016-01-11 14:10 ` Riku Voipio
2016-01-11 14:13 ` John Paul Adrian Glaubitz
2015-12-24 21:14 ` Laurent Vivier
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=567C60B9.6080208@vivier.eu \
--to=laurent@vivier.eu \
--cc=glaubitz@physik.fu-berlin.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).