Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: Tony Ambardar <tony.ambardar@gmail.com>, bpf@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
	Shuah Khan <shuah@kernel.org>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Quentin Monnet <qmo@kernel.org>
Subject: Re: [PATCH bpf-next v5 8/8] selftests/bpf: Support cross-endian building
Date: Tue, 3 Sep 2024 22:52:57 -0700	[thread overview]
Message-ID: <d09692a9-20d0-42a0-a4a5-aa3c21ed9451@linux.dev> (raw)
In-Reply-To: <419d9f3b772a09f1db62b9bc484cb1e69336a444.1725347944.git.tony.ambardar@gmail.com>


On 9/3/24 12:33 AM, Tony Ambardar wrote:
> Update Makefile build rules to compile BPF programs with target endianness
> rather than host byte-order. With recent changes, this allows building the
> full selftests/bpf suite hosted on x86_64 and targeting s390x or mips64eb
> for example.
>
> Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>

LGTM.

Acked-by: Yonghong Song <yonghong.song@linux.dev>


      reply	other threads:[~2024-09-04  5:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  7:32 [PATCH bpf-next v5 0/8] libbpf, selftests/bpf: Support cross-endian usage Tony Ambardar
2024-09-03  7:32 ` [PATCH bpf-next v5 1/8] libbpf: Improve log message formatting Tony Ambardar
2024-09-03  7:32 ` [PATCH bpf-next v5 2/8] libbpf: Fix header comment typos for BTF.ext Tony Ambardar
2024-09-03  7:33 ` [PATCH bpf-next v5 3/8] libbpf: Fix output .symtab byte-order during linking Tony Ambardar
2024-09-03  7:33 ` [PATCH bpf-next v5 4/8] libbpf: Support BTF.ext loading and output in either endianness Tony Ambardar
2024-09-04 19:48   ` Andrii Nakryiko
2024-09-16  8:21     ` Tony Ambardar
2024-09-03  7:33 ` [PATCH bpf-next v5 5/8] libbpf: Support opening bpf objects of " Tony Ambardar
2024-09-04 19:50   ` Andrii Nakryiko
2024-09-03  7:33 ` [PATCH bpf-next v5 6/8] libbpf: Support linking " Tony Ambardar
2024-09-04 19:51   ` Andrii Nakryiko
2024-09-03  7:33 ` [PATCH bpf-next v5 7/8] libbpf: Support creating light skeleton " Tony Ambardar
2024-09-03 19:57   ` Alexei Starovoitov
2024-09-03 23:52     ` Tony Ambardar
2024-09-03  7:33 ` [PATCH bpf-next v5 8/8] selftests/bpf: Support cross-endian building Tony Ambardar
2024-09-04  5:52   ` Yonghong Song [this message]

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=d09692a9-20d0-42a0-a4a5-aa3c21ed9451@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=iii@linux.ibm.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tony.ambardar@gmail.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