From: patchwork-bot+netdevbpf@kernel.org
To: Jie Meng <jmeng@fb.com>
Cc: kpsingh@kernel.org, bpf@vger.kernel.org, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf-next v2] bpf,x64: Remove unnecessary check on existence of SSE2
Date: Fri, 07 Oct 2022 14:30:16 +0000 [thread overview]
Message-ID: <166515301602.2538.7324165956325630888.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221005170039.3936894-1-jmeng@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 5 Oct 2022 10:00:39 -0700 you wrote:
> SSE2 and hence lfence are architectural in x86-64 and no need to check
> whether they're supported in CPU. SSE2's CPUID flag is still set to
> maintain backward compatibility with older code or code shared with x86,
> but bpf_jit_comp.c is compiled under x86-64 exclusively so the check is
> redundant.
>
> Signed-off-by: Jie Meng <jmeng@fb.com>
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf,x64: Remove unnecessary check on existence of SSE2
https://git.kernel.org/bpf/bpf-next/c/2e30960097f6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-07 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 1:17 [PATCH bpf-next] bpf,x64: Remove unnecessary check on existence of SSE2 Jie Meng
2022-10-04 1:04 ` KP Singh
2022-10-04 3:50 ` Jie Meng
2022-10-05 0:30 ` KP Singh
2022-10-05 17:00 ` [PATCH bpf-next v2] " Jie Meng
2022-10-06 0:58 ` KP Singh
2022-10-07 14:30 ` patchwork-bot+netdevbpf [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=166515301602.2538.7324165956325630888.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jmeng@fb.com \
--cc=kpsingh@kernel.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 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.