Skip to content
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

extra-events column names could use improvement #50

Closed
travisdowns opened this issue Jun 23, 2018 · 1 comment
Closed

extra-events column names could use improvement #50

travisdowns opened this issue Jun 23, 2018 · 1 comment

Comments

@travisdowns
Copy link
Owner

travisdowns commented Jun 23, 2018

When the user specifies --extra-events=... we need names for the column headers displaying those names. Currently we just take the first 6 characters of the event name, which sometimes isn't meaningful and often leads to duplicates when you have several related events all with the same first six characters.

We should do better. Perhaps smartly generate the name by taking characters from after the first or last underscore. This could even be dynamic: i.e,. check that no abbreviations end as duplicates based on the selected events and if there are, change the name generation so that they aren't.

Alternatives are possible, such as just calling the events EVT1, EVT2, etc, or adding more header rows to allow more characters, etc.

@travisdowns
Copy link
Owner Author

travisdowns commented Jan 26, 2020

You can now add column names by putting #name after each event definition, like this:

--extra-events=uops_dispatched_port.port_0#p0,uops_dispatched_port.port_1#p1,uops_dispatched_port.port_2#p2

This will give column names p0, p1 and p2.

travisdowns added a commit that referenced this issue Jan 26, 2020
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

No branches or pull requests

1 participant