Bug 440403 - Some Arm64 CPU feature is masked when valgrind is running and can not run the memcheck
Summary: Some Arm64 CPU feature is masked when valgrind is running and can not run the...
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-30 03:54 UTC by kevinz
Modified: 2021-10-29 17:50 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kevinz 2021-07-30 03:54:29 UTC
Background:
We are running PMDK on Arm64 for persistent memory operation. Now we meet an issue for running test suites. PMDK needs to check if Arm64 supports CPU feature: DCPOP, to decide to execute which CPU flushing command. 

But with the commit: https://bugs.kde.org/show_bug.cgi?id=381556, the CPU features have been masked, so we can not detect the real CPU features such as DCPOP. That will induce that we can not use cpu flushing cmd: "dc cvap" to flushing the CPU, which break the persistent memory working flow.

Is there any potential fix for this? Since Permsist memory is more and more important now, and memcheck for persist memory will be an important user scenario for valgrind.

ENV:
Arm v8.2 Qemu Guest:
processor	: 7
BogoMIPS	: 200.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfhm
CPU implementer	: 0x48
CPU architecture: 8
CPU variant	: 0x1
CPU part	: 0xd01
CPU revision	: 0