From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [PATCH v3 RESEND] kvm: vmx: Properly handle machine check during VM-entry Date: Fri, 30 Jun 2017 10:57:47 +0800 Message-ID: <7f58767f-1510-7c27-beb7-3fbb42510648@gmail.com> References: <20170629200116.177531-1-jmattson@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Jim Mattson , kvm list Return-path: Received: from mail-pf0-f181.google.com ([209.85.192.181]:32881 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751005AbdF3C5l (ORCPT ); Thu, 29 Jun 2017 22:57:41 -0400 Received: by mail-pf0-f181.google.com with SMTP id e7so59784844pfk.0 for ; Thu, 29 Jun 2017 19:57:41 -0700 (PDT) In-Reply-To: <20170629200116.177531-1-jmattson@google.com> Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: On 06/30/2017 04:01 AM, Jim Mattson wrote: > vmx_complete_atomic_exit should call kvm_machine_check for any > VM-entry failure due to a machine-check event. Such an exit should be > recognized solely by its basic exit reason (i.e. the low 16 bits of > the VMCS exit reason field). None of the other VMCS exit information > fields contain valid information when the VM-exit is due to "VM-entry > failure due to machine-check event". Reviewed-by: Xiao Guangrong