KernArmHook: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
==Synopsis== | ==Synopsis== | ||
VOID APIENTRY KernArmHook(ULONG hook,ULONG data); | VOID APIENTRY KernArmHook(ULONG hook,ULONG data,ULONG flags); | ||
==Parameters== | ==Parameters== | ||
;hook:Hook as returned from [[KernAllocateContextHook]]. | ;hook:Hook as returned from [[KernAllocateContextHook]]. | ||
;data:Data that is passed to the hook when called. | ;data:Data that is passed to the hook when called. | ||
;flags: unknown, set to 0. | |||
==Comments== | ==Comments== | ||
Revision as of 01:45, 6 December 2020
This is the 32 bit equivalent of DevHlp_ArmCtxHook.
Synopsis
VOID APIENTRY KernArmHook(ULONG hook,ULONG data,ULONG flags);
Parameters
- hook
- Hook as returned from KernAllocateContextHook.
- data
- Data that is passed to the hook when called.
- flags
- unknown, set to 0.
Comments
There is no such thing as a DevHlp_FreeCtxHook. I am unsure whether the hook handles are portable between 16 and 32 bit code. At least, this demonstrates that the KEE API has been tailored straight to its use in JFS and DASD, where one probably never needs to release a hook again.