Re: [Patch v5 1/4] Remove SMEP bit from CR4_RESERVED_BITS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/30/2011 11:52 AM, Ingo Molnar wrote:
* Avi Kivity<avi@xxxxxxxxxx>  wrote:

>  >  Another option would be to try to set the SMEP bit *before* we
>  >  enable paging. In theory this should not confuse a Linux guest -
>  >  and while i have not tested it i *think* we let it survive in the
>  >  saved_cr4_features shadow variable. That would make guest
>  >  suspend/resume work out of box as well.
>
>  Is there any reason not to do it in a hidden way in kvm?  Why must
>  we play tricks?

So do you have a suggestion of how to do this cleaner?

Add an ioctl that allows a VCPU to be configured in a way to set a
cr4 feature without the guest actually seeing that bit? [Assuming
both cr4 reads and writes are fully captured by KVM and thus guest
behavior is controllable.]

Yes, this was what I suggested before.  IIRC you liked it.

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux