This is a long shot... but is there any way how to allocate such non-paged kernel memory, that MiScrubMemoryWorker (called by NtSetSystemInformation(SystemScrubPhysicalMemoryInformation, ...) won't touch it?
-
Show this thread
-
-
Replying to @aionescu
In short: when MiScrubMemoryWorker is triggered, it (roughly) unmaps some PTE, calls RDTSC and then maps the PTE again. Now when you have "blue pill"-like hypervisor and enable RDTSC trapping, it might crash, because some of the HV page is unmapped.
1 reply 0 retweets 1 like -
Replying to @PetrBenes @aionescu
...so I was wondering whether there's simple hacky workaround this
1 reply 0 retweets 0 likes
Replying to @PetrBenes @aionescu
going semi-type-1 when runtime is neither hacky nor simple but does work. I'm not sure how I should call this though, type 1.5? On the other hand, have you tried MmAllocateIndependentPages yet?
3:56 PM - 6 Sep 2019
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.