{"id":1182,"date":"2011-03-20T12:38:02","date_gmt":"2011-03-20T10:38:02","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=1182"},"modified":"2011-03-20T12:46:09","modified_gmt":"2011-03-20T10:46:09","slug":"obtaining-number-of-thread-context-switched","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/1182","title":{"rendered":"Obtaining number of thread context switches programmatically"},"content":{"rendered":"

Previous post on thread synchronization and context switches<\/a> used number of thread context switches as one of the performance indicators. One might have hard times getting the number from operating system though.<\/p>\n

The only well documented access to amount of context switches seems to be accessing corresponding performance counters<\/a>. Thread performance counter will list available thread instances and counters “Thread(<process-name>\/<thread-number>)\/Context Switches\/sec<\/em>” will provide context switch rate per second.<\/p>\n

\"\"<\/a><\/p>\n

While access to performance counters is far not the most convenient API, to access data programmatically one would really prefer absolute number of switches rather than rate per second (which is still good for interactive monitoring).<\/p>\n

A gate into kernel world to grab the data of interest is provided with NtQuerySystemInformation<\/a> function. Although mentioned in documentation, it is marked as unreliable for use, and Windows SDK static library is missing it so one has to obtain it using GetModuleHandle<\/a>\/GetProcAddress<\/a> it explicity.<\/p>\n

typedef<\/span> NTSTATUS (<\/span>WINAPI<\/span> *<\/span>NTQUERYSYSTEMINFORMATION)<\/span>(<\/span>SYSTEM_INFORMATION_CLASS SystemInformationClass,<\/span> PVOID<\/span> SystemInformation,<\/span> ULONG<\/span> SystemInformationLength,<\/span> PULONG<\/span> ReturnLength)<\/span>;<\/span>\r\nNTQUERYSYSTEMINFORMATION NtQuerySystemInformation =<\/span> (<\/span>NTQUERYSYSTEMINFORMATION)<\/span> GetProcAddress<\/span>(<\/span>GetModuleHandle<\/span>(<\/span>_T(<\/span>\"<\/span>ntdll.dll<\/span>\"<\/span>)<\/span>)<\/span>,<\/span> \"<\/span>NtQuerySystemInformation<\/span>\"<\/span>)<\/span>;<\/span>\r\nATLASSERT(<\/span>NtQuerySystemInformation)<\/span>;<\/span>\r\nATLVERIFY(<\/span>NtQuerySystemInformation(<\/span>.<\/span>.<\/span>.<\/span>)<\/span> =<\/span>=<\/span> 0<\/span>)<\/span>;<\/span><\/pre>\n
Having this done, the function is capable of providing SystemProcessInformation\/SYSTEM_PROCESS_INFORMATION data about running processes.<\/p>\n
MSDN documents only a part of the structure, and the rest of the data contains information of interest. Returned data contains a list of variable length SYSTEM_PROCESS_INFORMATION structures, each of which has a fixed part (partially documented on MSDN), and embeds list of variable length structures for every thread running within the process.<\/p>\n
For 32-bit Win32 platform, layout of the structure is documented on Internet, for example, here: SYSTEM_THREAD on Undocumented functions of NTDLL<\/a>.<\/p>\n
For 64-bit x64 (amd64) platform the access method works too, however I had to fit the structure layout so that it matches actual data:<\/p>\n
typedef<\/span> struct<\/span> _SYSTEM_THREAD_INFORMATION {<\/span>\r\n    ULONGLONG KernelTime;<\/span>\r\n    ULONGLONG UserTime;<\/span>\r\n    ULONGLONG CreateTime;<\/span>\r\n    ULONG<\/span> WaitTime;<\/span>\r\n    ULONG<\/span> Reserved1;<\/span>\r\n    PVOID<\/span> StartAddress;<\/span>\r\n    CLIENT_ID ClientId;<\/span>\r\n    KPRIORITY Priority;<\/span>\r\n    LONG<\/span> BasePriority;<\/span>\r\n    ULONG<\/span> ContextSwitchCount;<\/span>\r\n    ULONG<\/span> State;<\/span>\r\n    KWAIT_REASON WaitReason;<\/span>\r\n}<\/span> SYSTEM_THREAD_INFORMATION,<\/span> *<\/span>PSYSTEM_THREAD_INFORMATION;<\/span>\r\n\r\ntypedef<\/span> struct<\/span> _SYSTEM_PROCESS_INFORMATION {<\/span>\r\n    ULONG<\/span> NextEntryOffset;<\/span>\r\n    ULONG<\/span> NumberOfThreads;<\/span>\r\n    ULONGLONG Reserved[<\/span>3<\/span>]<\/span>;<\/span>\r\n    ULONGLONG CreateTime;<\/span>\r\n    ULONGLONG UserTime;<\/span>\r\n    ULONGLONG KernelTime;<\/span>\r\n    UNICODE_STRING ImageName;<\/span>\r\n    KPRIORITY BasePriority;<\/span>\r\n    HANDLE<\/span> ProcessId;<\/span>\r\n    HANDLE<\/span> InheritedFromProcessId;<\/span>\r\n    ULONG<\/span> HandleCount;<\/span>\r\n    ULONG<\/span> Reserved2[<\/span>2<\/span>]<\/span>;<\/span>\r\n    ULONG<\/span> PrivatePageCount;<\/span>  \/\/ Garbage<\/span>\r\n    VM_COUNTERS VirtualMemoryCounters;<\/span>\r\n    IO_COUNTERS IoCounters;<\/span>\r\n    SYSTEM_THREAD_INFORMATION Threads[<\/span>1<\/span>]<\/span>;<\/span>\r\n}<\/span> SYSTEM_PROCESS_INFORMATION,<\/span> *<\/span>PSYSTEM_PROCESS_INFORMATION;<\/span><\/pre>\n
Each structure contains thread identifier and related absolute number of context switches.<\/p>\n
Also, the same information is visually available from Process Explorer<\/a>:<\/p>\n
\"\"<\/a><\/p>\n
A more complete code snippet to access the data from x64 code is here in a small application\/project<\/a>, lines 18-144 within #pragma region<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Previous post on thread synchronization and context switches used number of thread context switches as one of the performance indicators. One might have hard times getting the number from operating system though. The only well documented access to amount of context switches seems to be accessing corresponding performance counters. Thread performance counter will list available… <\/p>\n
Read the full article<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21,13],"tags":[38,320,326,103,488,327,284],"class_list":["post-1182","post","type-post","status-publish","format-standard","hentry","category-seriously","category-source","tag-c","tag-context-switch","tag-ntdll","tag-performance","tag-source","tag-undocumented","tag-x64"],"_links":{"self":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/posts\/1182","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/comments?post=1182"}],"version-history":[{"count":0,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/posts\/1182\/revisions"}],"wp:attachment":[{"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/media?parent=1182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/categories?post=1182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/alax.info\/blog\/wp-json\/wp\/v2\/tags?post=1182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}