Hi,

Apologies if the answer to this is someplace I have not looked. I've searched 
this list and other sites/FAQ's. 

I've noticed that command listed in the subject line always yields

<not counted> cycles

unless the target process is suspended. I have noticed this with a few different
distributions. Is the fact that the target process has to be suspended at least
once a known design limitation or would it be considered a bug?

Thank you for your help.

Chris

--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to