-
Notifications
You must be signed in to change notification settings - Fork 585
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
Add cpu_type for Intel Alder Lake. #2997
Conversation
In case it's relevant. I noticed the "XSAVE Architectural LBR".
|
This looks a bit suspicious because it only seems to set the PKRU flag in 64-bit mode, but my guess at adding Line 129 in b8566d2
|
Disabling the PKRU saving code where that assertion is in, and then running with taskset -c 0-15 (P-cores only) yields:
Without taskset there's much more failures and it just hangs endlessly in some tests. |
We should use something like this right? |
Probably should factor out the code to get the right GdbRegister value for PKRU for the arch. |
With that fix:
|
Running some of the failing tests as root makes them pass. My system now has a bunch of stale |
Second attempt: Looks like some of the failures at least are intermittent.
|
perf_event_mmap*-no-syscallbuf is a known issue. The most interesting ones are probably x86/pkeys and prctl_caps. Based on those failures though I would expect that rr largely works on your system at this point and there's just a few minor issues to deal with. |
|
Does |
|
|
|
Does pkeys always fail in exactly the same way? |
Yes
|
What are the values of |
f556f46
to
81c8521
Compare
|
|
What's the kernel version? |
I don't understand what could be going on here. The test passed on AWS c5d.9xlarge, which behaves as expected: after the pkey_alloc syscall, the kernel has changed the PKRU register and we record that in ExtraRegisters in the trace, and we restore those registers from the trace during replay. So I wonder if kernel behavior has changed somehow so that the PKRU changes aren't visible to rr for some reason. |
I think it makes sense to just merge this so I've don so. Please file a new issue for the pkeys test failure. |
5.14.21 |
This adds the
cpu_type
definition, which is enough to make most 64-bits tests pass. All 32-bit tests fail with1358: rr: ../src/ExtraRegisters.cc:665: void rr::ExtraRegisters::reset(): Assertion `d.xsave_feature_bit == PKRU_FEATURE_BIT' failed.
Still investigating that.