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

ucevent CBO.LLC_{DDIO,PCIE}_* events for HSX #21

Closed
tootoonchian opened this issue Mar 22, 2015 · 5 comments
Closed

ucevent CBO.LLC_{DDIO,PCIE}_* events for HSX #21

tootoonchian opened this issue Mar 22, 2015 · 5 comments
Labels

Comments

@tootoonchian
Copy link

Haswell Xeon CBO.LLC_{DDIO,PCIE}_* events are missing. Any plans to add them in the near future?

@andikleen
Copy link
Owner

You can in theory copy jkt_extra.py to hsx_extra.py to enable those.
Let me know if it works.

@tootoonchian
Copy link
Author

I don't think it is working correctly and I couldn't find Haswell uncore manual to verify if anything has changed.

CBO.LLC_DDIO_MEM_READ_BYTES and CBO.LLC_PCIE_MEM_READ_BYTES seem to always report 0 on Haswell but report correctly on Ivy Bridge. I cannot trust the write numbers either (running and comparing the same workload on Ivy Bridge).

On Haswell:

CBO.LLC_DDIO_MEM_WRITE_BYTES
|            CBO.LLC_DDIO_MEM_READ_BYTES
|            |    CBO.LLC_PCIE_MEM_WRITE_BYTES
|            |    |              CBO.LLC_PCIE_MEM_READ_BYTES
1,592,320.00 0.00 410,446,592.00 0.00  
1,593,088.00 0.00 410,517,248.00 0.00  

On Ivy Bridge:

CBO.LLC_DDIO_MEM_WRITE_BYTES
|            CBO.LLC_DDIO_MEM_READ_BYTES
|            |      CBO.LLC_PCIE_MEM_WRITE_BYTES
|            |      |                CBO.LLC_PCIE_MEM_READ_BYTES
17,408.00    0.00   5,046,370,432.00 3,571,441,472.00 
16,896.00    0.00   5,046,201,536.00 3,571,521,088.00 

@andikleen
Copy link
Owner

@tootoonchian
Copy link
Author

Thanks for the link. Just took a quick look at the manual. There doesn't seem to be any changes.

@andikleen
Copy link
Owner

Unlikely to fix anything for Haswell anymore at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants