Predicting_real_estate_prices_using_scikit-learn icon indicating copy to clipboard operation
Predicting_real_estate_prices_using_scikit-learn copied to clipboard

Published 20 hours ago • verified publisher icon MBKraus

** WIP ** Grouping trap handlers together for ease of checking TrapHandler->Eip ranges.

Open HBelusca opened this issue 6 years ago • 14 comments

Purpose

A better & more robust solution for PRs #1996 and #1997 ?

For checking whether we are in a TSS I think we can look at the contents of the CPU TR register and compare with the known TSS selector values: KGDT_DF_TSS (Double-Fault), KGDT_NMI_TSS (NMI), KGDT_TSS (the boot TSS). With that it may be actually possible to just go ahead and deal with any TSS presently active, and group both functions KdbpInNmiOrDoubleFaultHandler() and KdbpTrapFrameFromPrevTss() together...

NOTE: Only KiTrap0DHandler() is the only handler that seems to really require an Eip range check.

JIRA issue: CORE-16448

HBelusca avatar Oct 28 '19 00:10 HBelusca