search

intel / IntelSEAPI

IntelSEAPI
201 stars 53 forks source link

test_win.bat strange results? #14

Open red1939 opened 7 years ago

red1939 commented 7 years ago

To verify if the SEAPI works correctly I ran the test_win.bat. There are couple of issues that I see and I am wondering if they can be safely ignored.

First, xperf complains that:

xperf: error: NT Kernel Logger: The instance name passed was not recognized as valid by a WMI data provider. (0x1069)

However the capturing proceeds and results are gathered. I opened the resulting file in chrome tracing and apart from expected stuff like Worker Thread 2 (or main) with slices (denoting functions) I got a lot of sampled entries like:

main: AllocHook main: CRecursionScope main: operator new main: std::chrono::duration ...

Can I get rid of them, and why they are there? Shouldn't they be placed at the same line as main/Worker Thread 1/Worker Thread 2 so that when I click on specific time moment in a task I can see what was executed?

araud commented 7 years ago

There are two problems you observe: First is the attempt to shutdown NT Kernel Logger before start of new collection. This is important because NT Kernel Logger is one global singleton and any other profiler might left it collecting. Would be better first check if NT Kernel Logger is in use before trying to kill it, then you wouldn't see the message on attempt to shut down it when it was not in fact used. Please feel free to contribute this change, when you have time! :) This project is open source for the good reason - you can improve it and everyone's life better! As I can't promise you to address this issue in near future. This is just an annoying message after all, not a functional problem.

Second problem I don't understand clearly, could you please create separate issue for it and give better explanation? Are you talking about stacks collection? If yes, you can remove --stacks from the .bat file