KernArmHook: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
This is the 32 bit equivalent of DevHlp_ArmCtxHook. | |||
==Synopsis== | ==Synopsis== | ||
VOID APIENTRY KernArmHook(ULONG hook,ULONG data); | VOID APIENTRY KernArmHook(ULONG hook,ULONG data); | ||
==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. | ||
==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]] | ||
Revision as of 12:18, 19 July 2020
This is the 32 bit equivalent of DevHlp_ArmCtxHook.
Synopsis
VOID APIENTRY KernArmHook(ULONG hook,ULONG data);
Parameters
- hook
- Hook as returned from KernAllocateContextHook.
- data
- Data that is passed to the hook when called.
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.