KernArmHook: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This is the 32 bit equivalent of [[DevHelp_ArmCtxHook]]. | |||
==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'' ([[ULONG]]) - input:Hook as returned from [[KernAllocateContextHook]]. | ||
;data:Data that is passed to the hook when called. | ;''data'' ([[ULONG]]) - input:Data that is passed to the hook when called. | ||
;''flags'' ([[ULONG]]) - input: Unused, set to 0. | |||
==Comments== | ==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. | 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. | ||
[[Category:KEE]] | [[Category:KEE]] | ||
Latest revision as of 03:03, 28 May 2025
This is the 32 bit equivalent of DevHelp_ArmCtxHook.
Synopsis
VOID APIENTRY KernArmHook(ULONG hook,ULONG data,ULONG flags);
Parameters
- hook (ULONG) - input
- Hook as returned from KernAllocateContextHook.
- data (ULONG) - input
- Data that is passed to the hook when called.
- flags (ULONG) - input
- Unused, 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.