cregit-Linux how code gets into the kernel

Release 4.12 tools/testing/selftests/bpf/bpf_endian.h

#ifndef __BPF_ENDIAN__

#define __BPF_ENDIAN__

#include <linux/swab.h>

/* LLVM's BPF target selects the endianness of the CPU
 * it compiles on, or the user specifies (bpfel/bpfeb),
 * respectively. The used __BYTE_ORDER__ is defined by
 * the compiler, we cannot rely on __BYTE_ORDER from
 * libc headers, since it doesn't reflect the actual
 * requested byte order.
 *
 * Note, LLVM's BPF target has different __builtin_bswapX()
 * semantics. It does map to BPF_ALU | BPF_END | BPF_TO_BE
 * in bpfel and bpfeb case, which means below, that we map
 * to cpu_to_be16(). We could use it unconditionally in BPF
 * case, but better not rely on it, so that this header here
 * can be used from application and BPF program side, which
 * 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)
#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)
#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))

#endif /* __BPF_ENDIAN__ */

Overall Contributors

PersonTokensPropCommitsCommitProp
David S. Miller6462.75%150.00%
Daniel Borkmann3837.25%150.00%
Total102100.00%2100.00%
Information contained on this website is for historical information purposes only and does not indicate or represent copyright ownership.
Created with cregit.