From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, tsbogend@alpha.franken.de,
johan.almbladh@anyfinetworks.com, paulburton@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v2 1/2] MIPS: ebpf jit: Implement DADDI workarounds
Date: Tue, 28 Feb 2023 13:02:22 +0100 [thread overview]
Message-ID: <6198f1c8-29b7-dba4-2469-2a99eb03c83e@linaro.org> (raw)
In-Reply-To: <20230228113305.83751-2-jiaxun.yang@flygoat.com>
On 28/2/23 12:33, Jiaxun Yang wrote:
> For DADDI errata we just workaround by disable immediate operation
> for BPF_ADD / BPF_SUB to avoid generation of DADDIU.
>
> All other use cases in JIT won't cause overflow thus they are all safe.
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> v2: Drop 64BIT ifdef
> ---
> arch/mips/Kconfig | 1 -
> arch/mips/net/bpf_jit_comp.c | 4 ++++
> 2 files changed, 4 insertions(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-02-28 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 11:33 [PATCH v2 0/2] MIPS: Implement two workarounds for BPF JIT Jiaxun Yang
2023-02-28 11:33 ` [PATCH v2 1/2] MIPS: ebpf jit: Implement DADDI workarounds Jiaxun Yang
2023-02-28 12:02 ` Philippe Mathieu-Daudé [this message]
2023-02-28 12:35 ` Johan Almbladh
2023-02-28 11:33 ` [PATCH v2 2/2] MIPS: ebpf jit: Implement R4000 workarounds Jiaxun Yang
2023-02-28 14:00 ` [PATCH v2 0/2] MIPS: Implement two workarounds for BPF JIT patchwork-bot+netdevbpf
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=6198f1c8-29b7-dba4-2469-2a99eb03c83e@linaro.org \
--to=philmd@linaro.org \
--cc=bpf@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=johan.almbladh@anyfinetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).