From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: ast@kernel.org, rongtao@cestc.cn, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] samples/bpf: sampleip: Replace PAGE_OFFSET with _text address
Date: Fri, 14 Apr 2023 05:00:18 +0000 [thread overview]
Message-ID: <168144841833.15631.13621906411844041748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_A0E82E0BEE925285F8156D540731DF805F05@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 12 Apr 2023 16:16:24 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> Macro PAGE_OFFSET(0xffff880000000000) in sampleip_user.c is inaccurate,
> for example, in aarch64 architecture, this value depends on the
> CONFIG_ARM64_VA_BITS compilation configuration, this value defaults to 48,
> the corresponding PAGE_OFFSET is 0xffff800000000000, if we use the value
> defined in sampleip_user.c, then all KSYMs obtained by sampleip are (user)
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: sampleip: Replace PAGE_OFFSET with _text address
https://git.kernel.org/bpf/bpf-next/c/4a1e885c6d14
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-14 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 8:16 [PATCH bpf-next] samples/bpf: sampleip: Replace PAGE_OFFSET with _text address Rong Tao
2023-04-14 5:00 ` patchwork-bot+netdevbpf [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=168144841833.15631.13621906411844041748.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).