From: Daniel Borkmann <daniel@iogearbox.net>
To: David Daney <david.daney@cavium.com>,
Alexei Starovoitov <ast@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, ralf@linux-mips.org
Cc: Markos Chandras <markos.chandras@imgtec.com>
Subject: Re: [PATCH 5/5] MIPS: Add support for eBPF JIT.
Date: Fri, 26 May 2017 17:14:04 +0200 [thread overview]
Message-ID: <5928463C.5000204@iogearbox.net> (raw)
In-Reply-To: <20170526003826.10834-6-david.daney@cavium.com>
On 05/26/2017 02:38 AM, David Daney wrote:
> Since the eBPF machine has 64-bit registers, we only support this in
> 64-bit kernels. As of the writing of this commit log test-bpf is showing:
>
> test_bpf: Summary: 316 PASSED, 0 FAILED, [308/308 JIT'ed]
>
> All current test cases are successfully compiled.
>
> Signed-off-by: David Daney <david.daney@cavium.com>
Awesome work!
Did you also manage to run tools/testing/selftests/bpf/ fine with
the JIT enabled?
[...]
> +struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog)
> +{
> + struct jit_ctx ctx;
> + unsigned int alloc_size;
> +
> + /* Only 64-bit kernel supports eBPF */
> + if (!IS_ENABLED(CONFIG_64BIT) || !bpf_jit_enable)
Isn't this already reflected by the following?
select HAVE_EBPF_JIT if (64BIT && !CPU_MICROMIPS)
> + return prog;
> +
> + memset(&ctx, 0, sizeof(ctx));
> +
> + ctx.offsets = kcalloc(prog->len + 1, sizeof(*ctx.offsets), GFP_KERNEL);
> + if (ctx.offsets == NULL)
> + goto out;
> +
> + ctx.reg_val_types = kcalloc(prog->len + 1, sizeof(*ctx.reg_val_types), GFP_KERNEL);
> + if (ctx.reg_val_types == NULL)
> + goto out;
> +
> + ctx.skf = prog;
> +
> + if (reg_val_propagate(&ctx))
> + goto out;
> +
> + /* First pass discovers used resources */
> + if (build_int_body(&ctx))
> + goto out;
> +
> + /* Second pass generates offsets */
> + ctx.idx = 0;
> + if (gen_int_prologue(&ctx))
> + goto out;
> + if (build_int_body(&ctx))
> + goto out;
> + if (build_int_epilogue(&ctx))
> + goto out;
> +
> + alloc_size = 4 * ctx.idx;
> +
> + ctx.target = module_alloc(alloc_size);
You would need to use bpf_jit_binary_alloc() like all other
eBPF JITs do, otherwise kallsyms of the JITed progs would
break.
> + if (ctx.target == NULL)
> + goto out;
> +
> + /* Clean it */
> + memset(ctx.target, 0, alloc_size);
> +
> + /* Third pass generates the code */
> + ctx.idx = 0;
> + if (gen_int_prologue(&ctx))
> + goto out;
> + if (build_int_body(&ctx))
> + goto out;
> + if (build_int_epilogue(&ctx))
> + goto out;
> + /* Update the icache */
> + flush_icache_range((ptr)ctx.target, (ptr)(ctx.target + ctx.idx));
> +
> + if (bpf_jit_enable > 1)
> + /* Dump JIT code */
> + bpf_jit_dump(prog->len, alloc_size, 2, ctx.target);
> +
> + prog->bpf_func = (void *)ctx.target;
> + prog->jited = 1;
> +
> +out:
> + kfree(ctx.offsets);
> + kfree(ctx.reg_val_types);
> +
> + return prog;
> +}
next prev parent reply other threads:[~2017-05-26 15:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 0:38 [PATCH 0/5] MIPS: Implement eBPF JIT David Daney
2017-05-26 0:38 ` [PATCH 1/5] MIPS: Optimize uasm insn lookup David Daney
2017-05-26 8:07 ` Matt Redfearn
2017-05-26 18:25 ` David Daney
2017-05-26 0:38 ` [PATCH 2/5] MIPS: Correctly define DBSHFL type instruction opcodes David Daney
2017-05-26 0:38 ` [PATCH 3/5] MIPS: Add some instructions to uasm David Daney
2017-05-26 0:38 ` [PATCH 4/5] MIPS: Sort uasm enum opcode elements David Daney
2017-05-26 0:38 ` [PATCH 5/5] MIPS: Add support for eBPF JIT David Daney
2017-05-26 2:23 ` Alexei Starovoitov
2017-05-26 16:10 ` David Daney
2017-05-26 15:14 ` Daniel Borkmann [this message]
2017-05-26 15:35 ` Daniel Borkmann
2017-05-26 15:39 ` David Daney
2017-05-26 19:09 ` Daniel Borkmann
2017-05-26 19:20 ` David Daney
2017-05-26 19:22 ` Daniel Borkmann
2017-05-26 15:29 ` David Miller
2017-05-26 17:12 ` kbuild test robot
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=5928463C.5000204@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=david.daney@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
/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).