-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Remove exclude guest flag from perf event attrs. #2640
Conversation
Hi @Creatone. Thanks for your PR. I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
Can we make it configurable? We did it for a reason in WCA, I guess. |
What is this flag responsible for? |
To not measure events inside VM. Why omit VM when we depend on measures from cgroups? |
I don't remember the exact reason, why we exclude VMs from measurement in WCA. Perhaps it has something to do with specific environment we planned to measure. |
IMHO there is no reason to omit VM measurements by default at all - I strongly recommend removing this flag because it will result in misleading results for virtual environments - we're going to remove that from WCA as well. |
The only reason I could think of is to actually prevent to count anything from hypervisor, perhaps to detect a process, which could grab the resources VM wants, thus performance of VM is affected. I'd opt for @iwankgb proposal to make it configurable. |
Sure, but where keep value? Another flag or in a perf config file? |
I think that we can extend config file. |
25864fc
to
4821bbf
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@iwankgb What do you think about proposed form of configuration? |
Can we use counters that take hypervisor into consideration and those that do not in a single group? |
We assumed it would be possible when event grouping would be available ( #2578 ). |
Sorry for the slow review. Based on the discussion, i'm a little concerned we don't have real use-cases for the additional configuration. It sounds like someone could use this in theory, but would anyone actually set this in practice? If we are unsure if it is needed, we should err on the side of omitting it for now, and doing what will work for most. We can always add it in later if there is a real need. |
4821bbf
to
a58eb48
Compare
I agree with you. |
598d38b
to
5f93c5c
Compare
Signed-off-by: Paweł Szulik <pawel.szulik@intel.com>
5f93c5c
to
728879c
Compare
@bobbypage your involvement here would be more than appreciated. |
@bobbypage thanks to this PR, perf events would be accurate for VMs. Could you check this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Sorry, didn't see the most recent commit removing the flag. This looks good now. |
From https://man7.org/linux/man-pages/man2/perf_event_open.2.html :
Depend on the kernel version,
perf_event_open
can throwinvalid_argument
for uncore events with this flag set.For core events it's also unnecessary.
Signed-off-by: Paweł Szulik pawel.szulik@intel.com