New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Some tips to optimize the library #15

Open

TanakaYasen opened this issue Dec 5, 2019 · 1 comment

TanakaYasen commented Dec 5, 2019

would you like to restore _WMI_LOGGER_CONTEXT::GetCpuClock in IfhRelease as a complete release.

I haven't tried yet though, is there a need to scan stack by INFINITYHOOK_MAGIC_1 INFINITYHOOK_MAGIC_2 every time enter syscall. AFAIK it hurts perfermance to some extent. or maybe when enter KiSystemCall64 , address of [rsp+138h+Var_f8] is a fixed offset to PVOID* StackMax = (PVOID*)__readgsqword(OFFSET_KPCR_RSP_BASE) .

The text was updated successfully, but these errors were encountered:

SpriteOvO commented May 11, 2020

would you like to restore _WMI_LOGGER_CONTEXT::GetCpuClock in IfhRelease as a complete release.

Restarting the CKCL session will restore the GetCpuClock pointer to its original value, so there is no need to restore it manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment