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

marker API for likwid-perfCtr not working #34

Closed
GoogleCodeExporter opened this issue Sep 28, 2015 · 2 comments
Closed

marker API for likwid-perfCtr not working #34

GoogleCodeExporter opened this issue Sep 28, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Instrument the code as described in:
http://code.google.com/p/likwid/wiki/Introduction

2. Run the command
./likwid-perfCtr -m  -c 0  -g L2  ./likwid-pin -c 0 <executable>


3.

What is the expected output? What do you see instead?

Expected output: the hardware counter information
Actual output: The message: "WARNING: Number of threads in marker file unequal 
to number of threads in likwid-perfCtr!"

and No output is seen.

What version of the product are you using? On what operating system?
Using 1.0.
On linux

Please provide any additional information below.


Original issue reported on code.google.com by sanket.t...@gmail.com on 13 Jul 2010 at 2:51

@GoogleCodeExporter
Copy link
Author

Usually this is due to multiple calls to the marker API
in your measured code.

Without an code example it is difficult for me to help.

It is important that you install likwid-pin to work correctly with make install.
You execute the program serial above. If it is a threaded program you have to 
measure the same number of threads you intrumented.

Find attached two examples for usage. One is serial (dofp.c) and one OpenMP 
parallel (openMP.c). If it works please let me know what part in the 
documentation maybe was not clear enough.

Original comment by jan.trei...@gmail.com on 21 Jul 2010 at 10:17

Attachments:

@GoogleCodeExporter
Copy link
Author

As I got no further answer I regard this issue as solved.
You might reopen it if there is still a problem.

Original comment by jan.trei...@gmail.com on 3 Aug 2010 at 8:46

  • Changed state: Fixed

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

No branches or pull requests

1 participant