From: David Miller <davem@davemloft.net>
To: andreas@gaisler.com
Cc: libc-alpha@sourceware.org, adhemerval.zanella@linaro.org,
carlos@redhat.com, triegel@redhat.com, software@gaisler.com
Subject: Re: [RFC][PATCH 1/2] sparc32: Mark sendmsg and recvmsg system calls as unsupported
Date: Fri, 04 Nov 2016 18:36:00 -0000 [thread overview]
Message-ID: <20161104.143626.1385309508547734948.davem@davemloft.net> (raw)
In-Reply-To: <1478012867-6031-2-git-send-email-andreas@gaisler.com>
From: Andreas Larsson <andreas@gaisler.com>
Date: Tue, 1 Nov 2016 16:07:46 +0100
> @@ -32,8 +32,10 @@
> #include_next <kernel-features.h>
>
> /* 32-bit SPARC kernels do not support
> - futex_atomic_cmpxchg_inatomic. */
> + futex_atomic_cmpxchg_inatomic or sendmsg/recvmsg. */
> #if !defined __arch64__ && !defined __sparc_v9__
> # undef __ASSUME_REQUEUE_PI
> # undef __ASSUME_SET_ROBUST_LIST
> +# undef __ASSUME_SENDMSG_SYSCALL
> +# undef __ASSUME_RECVMSG_SYSCALL
> #endif
As mentioned elsewhere, these are available on 4.4. and later kernels.
next prev parent reply other threads:[~2016-11-04 18:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:08 [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware Andreas Larsson
2016-11-01 15:08 ` [RFC][PATCH 1/2] sparc32: Mark sendmsg and recvmsg system calls as unsupported Andreas Larsson
2016-11-01 17:28 ` Adhemerval Zanella
2016-11-02 11:38 ` Andreas Larsson
2016-11-02 12:49 ` Adhemerval Zanella
2016-11-04 18:36 ` David Miller [this message]
2016-11-01 15:08 ` [RFC][PATCH 2/2] sparc32: Use cas for atomic_* operations and use general pthread_barrier_wait Andreas Larsson
2016-11-04 18:37 ` David Miller
2016-11-04 18:44 ` David Miller
2016-11-01 16:00 ` [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware Torvald Riegel
2016-11-01 16:09 ` David Miller
2016-11-01 16:46 ` Torvald Riegel
2016-11-01 16:51 ` David Miller
2016-11-02 10:05 ` Torvald Riegel
2016-11-02 11:29 ` Andreas Larsson
2016-11-02 15:32 ` David Miller
2016-11-02 22:33 ` Torvald Riegel
2016-11-03 2:52 ` David Miller
2016-11-03 15:39 ` Torvald Riegel
2016-11-03 17:22 ` David Miller
2016-11-03 18:41 ` Adhemerval Zanella
2016-11-03 20:33 ` David Miller
2016-11-03 21:29 ` Adhemerval Zanella
2016-11-03 22:25 ` Torvald Riegel
2016-11-04 10:28 ` Andreas Larsson
2016-11-04 15:23 ` David Miller
2016-11-04 13:55 ` Richard Henderson
2016-11-04 15:31 ` David Miller
2016-11-04 16:10 ` Richard Henderson
2016-11-04 14:04 ` Richard Henderson
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=20161104.143626.1385309508547734948.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adhemerval.zanella@linaro.org \
--cc=andreas@gaisler.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=software@gaisler.com \
--cc=triegel@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).