From: Stanislav Fomichev <sdf@fomichev.me>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Shuah Khan <shuah@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Stanislav Fomichev <sdf@google.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] bpf, tests: tweak endianness selection
Date: Tue, 19 Mar 2019 09:01:15 -0700 [thread overview]
Message-ID: <20190319160115.GD7431@mini-arch.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20190319023331.23207-1-sergey.senozhatsky@gmail.com>
On 03/19, Sergey Senozhatsky wrote:
> Not all compilers have __builtin_bswap16() and __builtin_bswap32(),
> thus not all compilers are able to compile the following code
> (bpf_htons):
>
> (__builtin_constant_p(x) ? \
> ___constant_swab16(x) : __builtin_bswap16(x))
>
> That's why, for instance, bpf_htons() doesn't work on GCC < 4.8:
>
> error: implicit declaration of function '__builtin_bswap16'
>
> We can use __builtin_bswap16() only if compiler has this built-in,
> that is, only if __HAVE_BUILTIN_BSWAP16__ is defined. Standard UAPI
> __swab16()/__swab32() take care of that, and, additionally, handle
> __builtin_constant_p() cases as well (if compiler doesn't provide
> builtin bswap with constants folding):
>
> #ifdef __HAVE_BUILTIN_BSWAP16__
> #define __swab16(x) (__u16)__builtin_bswap16((__u16)(x))
> #else
> #define __swab16(x) \
> (__builtin_constant_p((__u16)(x)) ? \
> ___constant_swab16(x) : \
> __fswab16(x))
> #endif
>
> So we can tweak selftests/bpf/bpf_endian.h and use UAPI
> __swab16()/__swab32().
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> ---
> tools/testing/selftests/bpf/bpf_endian.h | 37 +++++-------------------
> 1 file changed, 8 insertions(+), 29 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/bpf_endian.h b/tools/testing/selftests/bpf/bpf_endian.h
> index b25595ea4a78..ba06222963d5 100644
> --- a/tools/testing/selftests/bpf/bpf_endian.h
> +++ b/tools/testing/selftests/bpf/bpf_endian.h
> @@ -20,38 +20,17 @@
> * use different targets.
> */
> #if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
> -# define __bpf_ntohs(x) __builtin_bswap16(x)
> -# define __bpf_htons(x) __builtin_bswap16(x)
> -# define __bpf_constant_ntohs(x) ___constant_swab16(x)
> -# define __bpf_constant_htons(x) ___constant_swab16(x)
This breaks the build until your next patch is applied (in other
words, breaks bisection). Can we do it in three steps?
Convert to swab (without breaking existing tests), convert the tests,
remove unused __bpf_xyz defines?
Could you also send it as a series (git format-patch --thread)? Those
patches depend on each other. And pls use [PATCH bpf-next] ... subj.
> -# define __bpf_ntohl(x) __builtin_bswap32(x)
> -# define __bpf_htonl(x) __builtin_bswap32(x)
> -# define __bpf_constant_ntohl(x) ___constant_swab32(x)
> -# define __bpf_constant_htonl(x) ___constant_swab32(x)
> +# define bpf_ntohs(x) __swab16(x)
> +# define bpf_htons(x) __swab16(x)
> +# define bpf_ntohl(x) __swab32(x)
> +# define bpf_htonl(x) __swab32(x)
> #elif __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
> -# define __bpf_ntohs(x) (x)
> -# define __bpf_htons(x) (x)
> -# define __bpf_constant_ntohs(x) (x)
> -# define __bpf_constant_htons(x) (x)
> -# define __bpf_ntohl(x) (x)
> -# define __bpf_htonl(x) (x)
> -# define __bpf_constant_ntohl(x) (x)
> -# define __bpf_constant_htonl(x) (x)
> +# define bpf_ntohs(x) (x)
> +# define bpf_htons(x) (x)
> +# define bpf_ntohl(x) (x)
> +# define bpf_htonl(x) (x)
> #else
> # error "Fix your compiler's __BYTE_ORDER__?!"
> #endif
>
> -#define bpf_htons(x) \
> - (__builtin_constant_p(x) ? \
> - __bpf_constant_htons(x) : __bpf_htons(x))
> -#define bpf_ntohs(x) \
> - (__builtin_constant_p(x) ? \
> - __bpf_constant_ntohs(x) : __bpf_ntohs(x))
> -#define bpf_htonl(x) \
> - (__builtin_constant_p(x) ? \
> - __bpf_constant_htonl(x) : __bpf_htonl(x))
> -#define bpf_ntohl(x) \
> - (__builtin_constant_p(x) ? \
> - __bpf_constant_ntohl(x) : __bpf_ntohl(x))
> -
> #endif /* __BPF_ENDIAN__ */
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-03-19 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 2:33 [PATCH] bpf, tests: tweak endianness selection Sergey Senozhatsky
2019-03-19 16:01 ` Stanislav Fomichev [this message]
2019-03-20 1:51 ` Sergey Senozhatsky
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=20190319160115.GD7431@mini-arch.hsd1.ca.comcast.net \
--to=sdf@fomichev.me \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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