On Sat, Feb 24, 2018 at 01:47:37AM +, Tian, Kevin wrote:
> > From: Roger Pau Monné [mailto:roger@citrix.com]
> > Sent: Friday, February 23, 2018 6:18 PM
> >
> > On Fri, Feb 23, 2018 at 04:56:38AM +, Tian, Kevin wrote:
> > > > From: Roger Pau Monne [mailto:roger@citrix.com]
> > > >
> From: Roger Pau Monné [mailto:roger@citrix.com]
> Sent: Friday, February 23, 2018 6:18 PM
>
> On Fri, Feb 23, 2018 at 04:56:38AM +, Tian, Kevin wrote:
> > > From: Roger Pau Monne [mailto:roger@citrix.com]
> > > Sent: Tuesday, February 20, 2018 4:57 PM
> > >
> > > There a bunch of bit
On Fri, Feb 23, 2018 at 04:56:38AM +, Tian, Kevin wrote:
> > From: Roger Pau Monne [mailto:roger@citrix.com]
> > Sent: Tuesday, February 20, 2018 4:57 PM
> >
> > There a bunch of bits in CR4 that should be allowed to be set directly
> > by the guest without requiring Xen intervention, curr
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: Tuesday, February 20, 2018 4:57 PM
>
> There a bunch of bits in CR4 that should be allowed to be set directly
> by the guest without requiring Xen intervention, currently this is
> already done by passing through guest writes into the C
There a bunch of bits in CR4 that should be allowed to be set directly
by the guest without requiring Xen intervention, currently this is
already done by passing through guest writes into the CR4 used when
running in non-root mode, but taking an expensive vmexit in order to
do so.
xenalyze reports
