Skip to content

Conversation

@andikleen
Copy link

Here are two patches fixing autofdo for newer perf versions and for Atom CPUs.

Andi Kleen added 2 commits May 10, 2017 04:39
This keeps breaking autofdo. perf 4.7 always generates a TIME_CONV
event which causes create_gcov to fail.

This patch makes the perf parser ignore all the perf record
generated events.

To avoid this problem in the future I predicted the range
beyond the current records.
Older Atom CPUs don't have predicted/mispredicted bits in the LBR,
so set neither predicted nor mispredicted.

The perf reader has a sanity check that either of these bits
have to be set. Just remove the check.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@danielcdh
Copy link
Contributor

Andi, Thanks for the commit! Please sign the CLA and then I'll merge this pull request.

Thanks,
Dehao

@jacksgt
Copy link

jacksgt commented Sep 4, 2017

I just tested this branch on the latest Linux & perf (both compiled from 4.13) and after applying the patch autofdo could successfully read my perf inject files.

Thanks for the patch @andikleen !

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

Successfully merging this pull request may close these issues.

4 participants