Re: [PATCH v2] KVM: nVMX: vmread should not set rflags to specify success in case of #PF

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

 



On Mon, Jan 13, 2020 at 12:09:42PM -0800, Sean Christopherson wrote:
> On Sat, Dec 28, 2019 at 02:25:24PM +0800, linmiaohe wrote:
> > From: Miaohe Lin <linmiaohe@xxxxxxxxxx>
> > 
> > In case writing to vmread destination operand result in a #PF, vmread
> > should not call nested_vmx_succeed() to set rflags to specify success.
> > Similar to as done in VMPTRST (See handle_vmptrst()).
> > 
> > Reviewed-by: Liran Alon <liran.alon@xxxxxxxxxx>
> > Signed-off-by: Miaohe Lin <linmiaohe@xxxxxxxxxx>
> 
> Reviewed-by: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>

Gah, got trigger happy.  This could also have "Cc: stable@xxxxxxxxxxxxxxx".
With that, my Reviewed-by stands :-).



[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