Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
In wdm.h, i've found these:
#define InterlockedIncrement64 _InterlockedIncrement64 LONG64 InterlockedIncrement64 ( _Inout_ _Interlocked_operand_ LONG64 volatile *Addend );
But after some search "InterlockedIncrement" (https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-interlockedincrement) is the only one documented which takes a LONG argument:
LONG CDECL_NON_WVMPURE InterlockedIncrement( [in, out] LONG volatile *Addend );
So what is the proper way to increment a 64bit argument ? Should we just call InterlockedIncrement64 directly?
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Kernel Debugging | 16-20 October 2023 | Live, Online |
Developing Minifilters | 13-17 November 2023 | Live, Online |
Internals & Software Drivers | 4-8 Dec 2023 | Live, Online |
Writing WDF Drivers | 10-14 July 2023 | Live, Online |
Comments
That’s what I would do. I’d also file a bug on the docs, indicating the 64-bit variant is undocumented. I’m sure the doc writers will appreciate this, and if there happens to be some strange reason the decision to not doc the function is intentional, they’ll telll you.
Peter
Peter Viscarola
OSR
@OSRDrivers
note also that modern compilers implement these as intrinsics and emit the lock instructions directly. That may be why they aren't in this part of the documentation