From: Luke Nelson <luke.r.nels@gmail.com>
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: "Xi Wang" <xi.wang@gmail.com>, "Björn Töpel" <bjorn@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
kernel-team@cloudflare.com, Networking <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 1/4] bpf: define bpf_jit_alloc_exec_limit for riscv JIT
Date: Fri, 24 Sep 2021 08:28:53 -0700 [thread overview]
Message-ID: <CAB-e3NQNkzcv6hNW1ga0Zhi_DcUVr2Q88WaE1m+CCXtKhHQcmw@mail.gmail.com> (raw)
In-Reply-To: <20210924095542.33697-2-lmb@cloudflare.com>
> Expose the maximum amount of useable memory from the sparcv JIT.
sparcv -> riscv?
Otherwise lgtm!
Acked-by: Luke Nelson <luke.r.nels@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Luke Nelson <luke.r.nels@gmail.com>
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: "Xi Wang" <xi.wang@gmail.com>, "Björn Töpel" <bjorn@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
kernel-team@cloudflare.com, Networking <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 1/4] bpf: define bpf_jit_alloc_exec_limit for riscv JIT
Date: Fri, 24 Sep 2021 08:28:53 -0700 [thread overview]
Message-ID: <CAB-e3NQNkzcv6hNW1ga0Zhi_DcUVr2Q88WaE1m+CCXtKhHQcmw@mail.gmail.com> (raw)
In-Reply-To: <20210924095542.33697-2-lmb@cloudflare.com>
> Expose the maximum amount of useable memory from the sparcv JIT.
sparcv -> riscv?
Otherwise lgtm!
Acked-by: Luke Nelson <luke.r.nels@gmail.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-09-24 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 9:55 [PATCH bpf-next 0/4] Fix up bpf_jit_limit some more Lorenz Bauer
2021-09-24 9:55 ` Lorenz Bauer
2021-09-24 9:55 ` [PATCH bpf-next 1/4] bpf: define bpf_jit_alloc_exec_limit for riscv JIT Lorenz Bauer
2021-09-24 9:55 ` Lorenz Bauer
2021-09-24 15:28 ` Luke Nelson [this message]
2021-09-24 15:28 ` Luke Nelson
2021-09-24 9:55 ` [PATCH bpf-next 2/4] bpf: define bpf_jit_alloc_exec_limit for arm64 JIT Lorenz Bauer
2021-09-24 9:55 ` Lorenz Bauer
2021-09-29 16:18 ` Will Deacon
2021-09-29 16:18 ` Will Deacon
2021-09-24 9:55 ` [PATCH bpf-next 3/4] bpf: prevent increasing bpf_jit_limit above max Lorenz Bauer
2021-09-24 9:55 ` [PATCH bpf-next 4/4] bpf: export bpf_jit_current Lorenz Bauer
2021-09-27 13:34 ` Daniel Borkmann
2021-09-27 14:01 ` Jakub Sitnicki
2021-09-28 9:02 ` Lorenz Bauer
2021-09-29 14:56 ` Nicolas Dichtel
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=CAB-e3NQNkzcv6hNW1ga0Zhi_DcUVr2Q88WaE1m+CCXtKhHQcmw@mail.gmail.com \
--to=luke.r.nels@gmail.com \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=xi.wang@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: 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.