I've recently discovered that if you attempt to use introspection to
capture CR3 changes with the new KPTI enabled kernels, the guest dies
shortly after the start of introspection with failed VM entry due to
invalid guest state.
I believe the invalid state here is the high bit being set in CR3 - w
x27;m
afraid I'm not very familiar with the Xen patch submission process.
Thank you!
-Bit
On Thu, Jan 25, 2018 at 8:07 AM, Razvan Cojocaru
wrote:
> On 01/25/2018 12:31 AM, Bitweasil . wrote:
> > I've recently discovered that if you attempt to use introspection to
> > ca
if ( (ad->monitor.write_ctrlreg_enabled & ctrlreg_bitmask) &&
(!(ad->monitor.write_ctrlreg_onchangeonly & ctrlreg_bitmask) ||
value != old) )
On Thu, Jan 25, 2018 at 4:03 PM, Razvan Cojocaru
wrote:
> On 01/26/2018 12:17 AM, Bitweasil . wrote:
>
reporting
performance hit under KPTI is quite catastrophic anyway, though I expect
one could mitigate that somewhat with CR3-targets, if one wanted to.
On Fri, Jan 26, 2018 at 12:39 AM Razvan Cojocaru
wrote:
> On 01/26/2018 02:02 AM, Bitweasil . wrote:
> > This also impacts the "
