From: Daniel Borkmann <daniel@iogearbox.net>
To: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>, bpf@vger.kernel.org
Cc: iii@linux.ibm.com, jolsa@redhat.com
Subject: Re: [PATCH v3] bpf: s390: add JIT support for multi-function programs
Date: Sat, 31 Aug 2019 01:22:08 +0200 [thread overview]
Message-ID: <f5ecc32b-b72f-df15-000e-3b2bf35192d0@iogearbox.net> (raw)
In-Reply-To: <20190828182846.10473-1-yauheni.kaliuta@redhat.com>
On 8/28/19 8:28 PM, Yauheni Kaliuta wrote:
> This adds support for bpf-to-bpf function calls in the s390 JIT
> compiler. The JIT compiler converts the bpf call instructions to
> native branch instructions. After a round of the usual passes, the
> start addresses of the JITed images for the callee functions are
> known. Finally, to fixup the branch target addresses, we need to
> perform an extra pass.
>
> Because of the address range in which JITed images are allocated on
> s390, the offsets of the start addresses of these images from
> __bpf_call_base are as large as 64 bits. So, for a function call,
> the imm field of the instruction cannot be used to determine the
> callee's address. Use bpf_jit_get_func_addr() helper instead.
>
> The patch borrows a lot from:
>
> commit 8c11ea5ce13d ("bpf, arm64: fix getting subprog addr from aux
> for calls")
>
> commit e2c95a61656d ("bpf, ppc64: generalize fetching subprog into
> bpf_jit_get_func_addr")
>
> commit 8484ce8306f9 ("bpf: powerpc64: add JIT support for
> multi-function programs")
>
> (including the commit message).
>
> test_verifier (5.3-rc6 with CONFIG_BPF_JIT_ALWAYS_ON=y):
>
> without patch:
> Summary: 1501 PASSED, 0 SKIPPED, 47 FAILED
>
> with patch:
> Summary: 1540 PASSED, 0 SKIPPED, 8 FAILED
>
> Signed-off-by: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Applied, thanks!
prev parent reply other threads:[~2019-08-30 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 18:20 [RFC PATCH] bpf: s390: add JIT support for multi-function programs Yauheni Kaliuta
2019-08-27 13:21 ` Ilya Leoshkevich
2019-08-27 13:46 ` Ilya Leoshkevich
2019-08-27 14:21 ` Yauheni Kaliuta
2019-08-27 14:37 ` Ilya Leoshkevich
2019-08-27 14:48 ` Yauheni Kaliuta
2019-08-27 14:25 ` Yauheni Kaliuta
2019-08-27 14:46 ` Ilya Leoshkevich
2019-08-27 15:05 ` Yauheni Kaliuta
2019-08-27 14:53 ` [PATCH v2] " Yauheni Kaliuta
2019-08-27 16:39 ` Ilya Leoshkevich
2019-08-28 9:11 ` Ilya Leoshkevich
2019-08-28 18:28 ` [PATCH v3] " Yauheni Kaliuta
2019-08-29 8:52 ` Ilya Leoshkevich
2019-08-30 23:22 ` Daniel Borkmann [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=f5ecc32b-b72f-df15-000e-3b2bf35192d0@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=iii@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=yauheni.kaliuta@redhat.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