From: "yikai.lin@vivo.com" <yikai.lin@vivo.com>
To: "Pu Lehui" <pulehui@huawei.com>
Cc: ast <ast@kernel.org>, daniel <daniel@iogearbox.net>,
andrii <andrii@kernel.org>, martin.lau <martin.lau@linux.dev>,
eddyz87 <eddyz87@gmail.com>, song <song@kernel.org>,
yonghong.song <yonghong.song@linux.dev>,
john.fastabend <john.fastabend@gmail.com>,
kpsingh <kpsingh@kernel.org>, sdf <sdf@fomichev.me>,
haoluo <haoluo@google.com>, jolsa <jolsa@kernel.org>,
mykolal <mykolal@fb.com>, shuah <shuah@kernel.org>,
terrelln <terrelln@fb.com>, bpf <bpf@vger.kernel.org>,
linux-kselftest <linux-kselftest@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
opensource.kernel <opensource.kernel@vivo.com>
Subject: Re: Re: [PATCH bpf-next v1 1/2] selftests/bpf: Update "vmtest.sh" for cross-compile arm64 on x86_64 host.
Date: Wed, 28 Aug 2024 11:11:47 +0800 [thread overview]
Message-ID: <2024082811104609509515@vivo.com> (raw)
In-Reply-To: f1dd704e-dfbd-496b-9466-83efe38c5287@huawei.com
On 2024-08-28 at 11:10:38, yikai.lin@vivo.com reply:
>
>On 2024/8/27 21:39, Lin Yikai wrote:
>> Identify "$CROSS_COMPILE" to enable vm_test for cross-compile situation.
>> Additionally, use "-cpu cortex-a57" flag to accommodate the majority of QEMU CPU lists,
>> avoiding using "-cpu host," which can cause qemu_system_aarch64 start failure on x86_64 host.
>>
>> Signed-off-by: Lin Yikai <yikai.lin@vivo.com>
>> ---
>> tools/testing/selftests/bpf/README.rst | 12 ++++++++-
>> tools/testing/selftests/bpf/vmtest.sh | 37 +++++++++++++++++++++-----
>> 2 files changed, 42 insertions(+), 7 deletions(-)
>>
>Hi Yikai,
>
>Your patch reminds me of a previous commit [0], which was able to
>support running vmtest in cross platform for all arch.
>
>Link:
>https://lore.kernel.org/all/20240328124916.293173-2-pulehui@huaweicloud.com/
>[0]
>
Hi, lehui, thank you for your reply.
I noticed you patch mainly targeted on riscv64 and also extended support to other ARCH.
While these changes are to have not been merged into the mainline yet.
Becuse currently I want to use and extend BPF on Android.
So my focus is primarily on cross-compiling for arm64 on x86.
next prev parent reply other threads:[~2024-08-28 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 13:39 [PATCH bpf-next v1 0/2] Enable vmtest for cross-compile arm64 on x86_64 host, and fix some related issues Lin Yikai
2024-08-27 13:39 ` [PATCH bpf-next v1 1/2] selftests/bpf: Update "vmtest.sh" for cross-compile arm64 on x86_64 host Lin Yikai
2024-08-27 14:05 ` Pu Lehui
2024-08-28 3:11 ` yikai.lin [this message]
2024-08-27 13:39 ` [PATCH bpf-next v1 2/2] selftests/bpf: Fix cross-compile issue for some files and a static compile issue for "-lzstd" Lin Yikai
2024-08-27 22:49 ` Andrii Nakryiko
2024-08-28 9:54 ` Yikai Lin
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=2024082811104609509515@vivo.com \
--to=yikai.lin@vivo.com \
--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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=opensource.kernel@vivo.com \
--cc=pulehui@huawei.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=terrelln@fb.com \
--cc=yonghong.song@linux.dev \
/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