Skip to content

[BPF] Fix dst/val mismatch in class ATOMIC_NOFETCH #107288

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 5, 2024

Conversation

yonghong-song
Copy link
Contributor

All ATOMIC_NOFETCH insns have "$dst = $val" constraints. So let us enforce "$dst = $val" having the same register type in ATOMIC_NOFETCH as well.

Currently, things work since ATOMIC_NOFETCH does not have source code pattern matching. I am experimenting to introduce memory ordering to BPFInstrInfo.td file and pattern matching will be needed. Eventually, for atomic_fetch_*() insns locked insns could be generated if memory ordering is memory_order_relaxed.

[1] https://lore.kernel.org/bpf/[email protected]/

All ATOMIC_NOFETCH insns have "$dst = $val" constraints. So let us enforce
"$dst = $val" having the same register type in ATOMIC_NOFETCH as well.

Currently, things work since ATOMIC_NOFETCH does not have source code
pattern matching. I am experimenting to introduce memory ordering
to BPFInstrInfo.td file and pattern matching will be needed. Eventually,
for atomic_fetch_*() insns locked insns could be generated if memory ordering
is memory_order_relaxed.

  [1] https://lore.kernel.org/bpf/[email protected]/
@yonghong-song yonghong-song merged commit ef1ef03 into llvm:main Sep 5, 2024
8 checks passed
@yonghong-song yonghong-song deleted the fix-atomic-nofetch branch September 12, 2024 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants