res-lock-arena #8613
Open
res-lock-arena #8613
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kkdwivedi
force-pushed
the
res-lock-arena
branch
from
34d6fec to
aa07147
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
2e18d02 to
a674d28
Compare
kkdwivedi
force-pushed
the
res-lock-arena
branch
2 times, most recently
from
157301d to
8f0fed9
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
4 times, most recently
from
9bdb3c5 to
762f3e0
Compare
kkdwivedi
force-pushed
the
res-lock-arena
branch
from
8f0fed9 to
9226489
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
9 times, most recently
from
b7965ce to
084fae2
Compare
kkdwivedi
force-pushed
the
res-lock-arena
branch
7 times, most recently
from
0a84181 to
759f206
Compare
kkdwivedi
force-pushed
the
res-lock-arena
branch
2 times, most recently
from
a8c385c to
9675f3b
Compare
Similar to how support for x86 JIT was done in commit 2cb0a52 ("bpf, x86: Add x86 JIT support for timed may_goto"), do a similar change for arm64 JIT. We use the same calling convention of using BPF_REG_AX (x9) as the first argument and return value from arch_bpf_timed_may_goto. Context for timed may_goto support is available in [0]. This change will allow arena_spin_lock primitives to be reliably used on arm64 machines without concerns around premature loop expiration under contention. Adjust the selftests again and now match on correct may_goto output only for s390. [0]: https://lore.kernel.org/bpf/[email protected] Cc: Xu Kuohai <[email protected]> Cc: Puranjay Mohan <[email protected]> Signed-off-by: Kumar Kartikeya Dwivedi <[email protected]>
Signed-off-by: Kumar Kartikeya Dwivedi <[email protected]>
kkdwivedi
force-pushed
the
res-lock-arena
branch
from
9675f3b to
7ce4a8e
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
2 times, most recently
from
44c3a1d to
720c696
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.