WINAPI

---

title: WIN API && QueryPerformanceCounter

---

计时

参考:MSDN

获取时钟频率=》获取2次计数差=》用时

QueryPerformanceFrequency() - 基本介绍

类型：Win32API
原型：BOOL QueryPerformanceFrequency(LARGE_INTEGER *lpFrequency);

作用：返回硬件支持的高精度计数器的频率。

返回值：非零，硬件支持高精度计数器；零，硬件不支持，读取失败。

QueryPerformanceFrequency() - 技术特点

供WIN9X使用的高精度定时器：QueryPerformanceFrequency()和QueryPerformanceCounter()，要求计算机从硬件上支持高精度定时器。需包含windows.h头文件。

函数的原形是：
BOOL QueryPerformanceFrequency(LARGE_INTEGER *lpFrequency);
BOOL QueryPerformanceCounter (LARGE_INTEGER *lpCount);

#if defined(MIDL_PASS)
typedef struct _LARGE_INTEGER {
#else // MIDL_PASS
typedef union _LARGE_INTEGER {
    struct {
        DWORD LowPart;
        LONG HighPart;
    } DUMMYSTRUCTNAME;
    struct {
        DWORD LowPart;
        LONG HighPart;
    } u;
#endif //MIDL_PASS
    LONGLONG QuadPart;
} LARGE_INTEGER;

LARGE_INTEGER StartingTime, EndingTime, ElapsedMicroseconds;
LARGE_INTEGER Frequency;

QueryPerformanceFrequency(&Frequency); 
QueryPerformanceCounter(&StartingTime);

// Activity to be timed

QueryPerformanceCounter(&EndingTime);
ElapsedMicroseconds.QuadPart = EndingTime.QuadPart - StartingTime.QuadPart;

//
// We now have the elapsed number of ticks, along with the
// number of ticks-per-second. We use these values
// to convert to the number of elapsed microseconds.
// To guard against loss-of-precision, we convert
// to microseconds *before* dividing by ticks-per-second.
//

ElapsedMicroseconds.QuadPart *= 1000000;
ElapsedMicroseconds.QuadPart /= Frequency.QuadPart;//微秒(us)

In general, the performance counter results are consistent across all processors in multi-core and multi-processor systems, even when measured on different threads or processes. Here are some exceptions to this rule:(在多核心和多处理器系统上,即使在不同线程或者不同处理器上计量,QPC的结果一致,除以下的特殊情况)
1: Pre-Windows Vista operating systems that run on certain processors might violate this consistency because of one of these reasons:(window visa之前的系统)
(1) The hardware processors have a non-invariant TSC and the BIOS doesn’t indicate this condition correctly.
(2) The TSC synchronization algorithm that was used wasn’t suitable for systems with large numbers of processors.
2:When you compare performance counter results that are acquired from different threads, consider values that differ by ± 1 tick to have an ambiguous ordering. If the time stamps are taken from the same thread, this ± 1 tick uncertainty doesn’t apply. In this context, the term tick refers to a period of time equal to 1 ÷ (the frequency of the performance counter obtained from QueryPerformanceFrequency).
The frequency of the performance counter is fixed at system boot and is consistent across all processors so you only need to query the frequency from QueryPerformanceFrequency as the application initializes, and then cache the result.(系统boot时已确定frequency不需要多次获取,在所有处理器上一致)

WINAPI

WINAPI见windef.h这个头文件,#define WINAPI __stdcall 同CALLBACK

转载:__stdcall

• __stdcall：

​ 1、进行函数调用，函数参数的入栈方式是最右边先入栈。

​ 2、同时__stdcall规定，被调函数负责栈的回收(调用者只负责压栈). 题外话：__pascal的调用规则是从左到右，正好与__stdcall相反。

• __cdecl

  （The C default calling convention）按从右至左的顺序压参数入栈，由调用者把参数弹出栈。对于传送参数的内存栈是由调用者来维护的（正因为如此，实现可变参数vararg的函数(如printf)只能使用该调用约定）当然，这些工作是应用程序自己完成的，不需要编写者动手。汇编语言另当别论（POP SP POP BP等） 。另外，在函数名修饰约定方面也有所不同。 _cdecl是C和C++程序的缺省调用方式。每一个调用它的函数都包含清空堆栈的代码，所以产生的可执行文件大小会比调用_stdcall函数的大。函数采用从右到左的压栈方式。

• 在函数调用过程中，会使用栈。__stdcall与__cdecl是两种不同的函数调用约定，定义了函数参数入栈的顺序，由调用函数还是被调用函数将参数弹出栈，以及产生函数修饰名的方法。关于这两个调用约定的详细信息，读者可参看MSDN。对于参数个数可变的函数，例如printf，使用的是__cdecl调用约定，Win32的API函数都遵循__stdcall调用约定。在VC++开发环境中，默认的编译选项是__cdecl，对于那些需要__stdcall调用约定的函数，在声明时必须显式地加上__stdcall。在Windows程序中，回调函数必须遵循__stdcall调用约定，所以我们在声明回调函数时要使用CALLBACK。使用CALLBACK而不是__cdecl的原因是为了告诉我们这是一个回调函数。