From: Xu Kuohai <xukuohai@huaweicloud.com> To: bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Daniel Borkmann <daniel@iogearbox.net>, Jean-Philippe Brucker <jean-philippe@linaro.org>, Alexei Starovoitov <ast@kernel.org>, Andrii Nakryiko <andrii@kernel.org>, Martin KaFai Lau <martin.lau@linux.dev>, Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>, John Fastabend <john.fastabend@gmail.com>, KP Singh <kpsingh@kernel.org>, Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>, Zi Shen Lim <zlim.lnx@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org> Subject: [RESEND PATCH bpf-next 0/2] Jit BPF_CALL to direct call when possible Date: Mon, 19 Sep 2022 05:21:36 -0400 [thread overview] Message-ID: <20220919092138.1027353-1-xukuohai@huaweicloud.com> (raw) Currently BPF_CALL is always jited to indirect call, but when target is in the range of direct call, a BPF_CALL can be jited to direct call. For example, the following BPF_CALL call __htab_map_lookup_elem is always jited to an indirect call: mov x10, #0xffffffffffff18f4 movk x10, #0x821, lsl #16 movk x10, #0x8000, lsl #32 blr x10 When the target is in the range of a direct call, it can be jited to: bl 0xfffffffffd33bc98 This patchset does such jit. Xu Kuohai (2): bpf, arm64: Jit BPF_CALL to direct call when possible bpf, arm64: Eliminate false -EFBIG error in bpf trampoline arch/arm64/net/bpf_jit_comp.c | 136 ++++++++++++++++++++++------------ 1 file changed, 87 insertions(+), 49 deletions(-) -- 2.30.2
WARNING: multiple messages have this Message-ID (diff)
From: Xu Kuohai <xukuohai@huaweicloud.com> To: bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Daniel Borkmann <daniel@iogearbox.net>, Jean-Philippe Brucker <jean-philippe@linaro.org>, Alexei Starovoitov <ast@kernel.org>, Andrii Nakryiko <andrii@kernel.org>, Martin KaFai Lau <martin.lau@linux.dev>, Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>, John Fastabend <john.fastabend@gmail.com>, KP Singh <kpsingh@kernel.org>, Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>, Zi Shen Lim <zlim.lnx@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org> Subject: [RESEND PATCH bpf-next 0/2] Jit BPF_CALL to direct call when possible Date: Mon, 19 Sep 2022 05:21:36 -0400 [thread overview] Message-ID: <20220919092138.1027353-1-xukuohai@huaweicloud.com> (raw) Currently BPF_CALL is always jited to indirect call, but when target is in the range of direct call, a BPF_CALL can be jited to direct call. For example, the following BPF_CALL call __htab_map_lookup_elem is always jited to an indirect call: mov x10, #0xffffffffffff18f4 movk x10, #0x821, lsl #16 movk x10, #0x8000, lsl #32 blr x10 When the target is in the range of a direct call, it can be jited to: bl 0xfffffffffd33bc98 This patchset does such jit. Xu Kuohai (2): bpf, arm64: Jit BPF_CALL to direct call when possible bpf, arm64: Eliminate false -EFBIG error in bpf trampoline arch/arm64/net/bpf_jit_comp.c | 136 ++++++++++++++++++++++------------ 1 file changed, 87 insertions(+), 49 deletions(-) -- 2.30.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-09-19 9:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-19 9:21 Xu Kuohai [this message] 2022-09-19 9:21 ` [RESEND PATCH bpf-next 0/2] Jit BPF_CALL to direct call when possible Xu Kuohai 2022-09-19 9:21 ` [RESEND PATCH bpf-next 1/2] bpf, arm64: " Xu Kuohai 2022-09-19 9:21 ` Xu Kuohai 2022-09-26 20:29 ` Daniel Borkmann 2022-09-26 20:29 ` Daniel Borkmann 2022-09-27 14:01 ` Xu Kuohai 2022-09-27 14:01 ` Xu Kuohai 2022-10-13 2:07 ` Xu Kuohai 2022-10-13 2:07 ` Xu Kuohai 2022-09-19 9:21 ` [RESEND PATCH bpf-next 2/2] bpf, arm64: Eliminate false -EFBIG error in bpf trampoline Xu Kuohai 2022-09-19 9:21 ` Xu Kuohai
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=20220919092138.1027353-1-xukuohai@huaweicloud.com \ --to=xukuohai@huaweicloud.com \ --cc=andrii@kernel.org \ --cc=ast@kernel.org \ --cc=bpf@vger.kernel.org \ --cc=catalin.marinas@arm.com \ --cc=daniel@iogearbox.net \ --cc=haoluo@google.com \ --cc=jean-philippe@linaro.org \ --cc=john.fastabend@gmail.com \ --cc=jolsa@kernel.org \ --cc=kpsingh@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=martin.lau@linux.dev \ --cc=sdf@google.com \ --cc=song@kernel.org \ --cc=will@kernel.org \ --cc=yhs@fb.com \ --cc=zlim.lnx@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.