From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: bpf@vger.kernel.org
Cc: daniel@iogearbox.net, iii@linux.ibm.com, jolsa@redhat.com
Subject: Re: [PATCH] bpf: s390: add JIT support for bpf line info
Date: Thu, 29 Aug 2019 19:16:41 +0300 [thread overview]
Message-ID: <xunyd0go9cba.fsf@redhat.com> (raw)
In-Reply-To: <20190829161330.14951-1-yauheni.kaliuta@redhat.com> (Yauheni Kaliuta's message of "Thu, 29 Aug 2019 19:13:30 +0300")
Hi!
Hold on, I should check it a bit more.
>>>>> On Thu, 29 Aug 2019 19:13:30 +0300, Yauheni Kaliuta wrote:
> This adds support for generating bpf line info for JITed programs
> like commit 6f20c71d8505 ("bpf: powerpc64: add JIT support for bpf
> line info") does for powerpc.
> Signed-off-by: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
> ---
> The patch is on top of "bpf: s390: add JIT support for multi-function
> programs"
> ---
> arch/s390/net/bpf_jit_comp.c | 1 +
> 1 file changed, 1 insertion(+)
> diff --git a/arch/s390/net/bpf_jit_comp.c b/arch/s390/net/bpf_jit_comp.c
> index b6801d854c77..4ef783b67dfc 100644
> --- a/arch/s390/net/bpf_jit_comp.c
> +++ b/arch/s390/net/bpf_jit_comp.c
> @@ -1420,6 +1420,7 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *fp)
> fp-> jited_len = jit.size;
> if (!fp->is_func || extra_pass) {
> + bpf_prog_fill_jited_linfo(fp, jit.addrs);
> free_addrs:
> kfree(jit.addrs);
> kfree(jit_data);
> --
> 2.22.0
--
WBR,
Yauheni Kaliuta
next prev parent reply other threads:[~2019-08-29 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 16:13 [PATCH] bpf: s390: add JIT support for bpf line info Yauheni Kaliuta
2019-08-29 16:16 ` Yauheni Kaliuta [this message]
2019-08-29 20:02 ` [PATCH v2] " Yauheni Kaliuta
2019-08-30 11:39 ` Ilya Leoshkevich
2019-08-30 11:47 ` Yauheni Kaliuta
2019-08-30 11:51 ` [PATCH v3] " Yauheni Kaliuta
2019-09-03 13:40 ` Daniel Borkmann
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=xunyd0go9cba.fsf@redhat.com \
--to=yauheni.kaliuta@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=iii@linux.ibm.com \
--cc=jolsa@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 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.