From: patchwork-bot+netdevbpf@kernel.org
To: Peter Zijlstra <peterz@infradead.org>
Cc: olsajiri@gmail.com, ast@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, bjorn@kernel.org, toke@redhat.com,
David.Laight@aculab.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing
Date: Fri, 04 Nov 2022 22:20:15 +0000 [thread overview]
Message-ID: <166760041503.11044.8727035971633367268.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221103120012.717020618@infradead.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 03 Nov 2022 13:00:12 +0100 you wrote:
> Hi!
>
> Even thought the __attribute__((patchable_function_entry())) solution to the
> BPF dispatcher woes works, it turns out to not be supported by the whole range
> of ageing compilers we support. Specifically this attribute seems to be GCC-8
> and later.
>
> [...]
Here is the summary with links:
- [1/2] bpf: Revert ("Fix dispatcher patchable function entry to 5 bytes nop")
(no matching commit)
- [2/2] bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace)
https://git.kernel.org/bpf/bpf/c/c86df29d11df
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-11-04 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:00 [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing Peter Zijlstra
2022-11-03 12:00 ` [PATCH 1/2] bpf: Revert ("Fix dispatcher patchable function entry to 5 bytes nop") Peter Zijlstra
2022-11-03 12:00 ` [PATCH 2/2] bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace) Peter Zijlstra
2022-11-14 17:36 ` Steven Rostedt
2022-11-03 13:42 ` [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing Björn Töpel
2022-11-03 14:48 ` Jiri Olsa
2022-11-04 22:20 ` 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=166760041503.11044.8727035971633367268.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=David.Laight@aculab.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=toke@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox