-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support platform/system domain in several access mechanisms #8
Comments
Dear @tilsche , this ticket does not describe whats wrong, but what's fixed, which makes it hard to comprehend. However, I think that's merged by now. Could I get access to the system you're talking check the x86_adapt / msr part? I would also do some rewriting to make it more robust. What would you suggest as the default mechanism? I'd go with sysfs due to the lowest privilege level required. |
Dear @tilsche, please try branch fix_issue_8 |
Looks good with the example (that failed previously):
(I have no /dev/msr on the system) Thanks |
With c83db45, it works with perf on my system.
I also tested sysfs where it fails.
setup
assumes all domains have/name
a like"package-<N>"
. The name is actuallypsys
. Everything fails then...Did not yet test x86_adapt or msr.
If we don't want to support it with all access methods, it should be documented and we should consider picking a method that generally works and prioritize that.
The text was updated successfully, but these errors were encountered: