From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH v3 59/75] x86/sev-es: Handle MONITOR/MONITORX Events Date: Fri, 12 Jun 2020 11:25:49 +0200 Message-ID: <20200612092549.GB3701@8bytes.org> References: <20200428151725.31091-1-joro@8bytes.org> <20200428151725.31091-60-joro@8bytes.org> <20200520063845.GC17090@linux.intel.com> <20200611131045.GE11924@8bytes.org> <20200611171305.GJ29918@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Tom Lendacky Cc: Sean Christopherson , x86@kernel.org, hpa@zytor.com, Andy Lutomirski , Dave Hansen , Peter Zijlstra , Thomas Hellstrom , Jiri Slaby , Dan Williams , Juergen Gross , Kees Cook , David Rientjes , Cfir Cohen , Erdem Aktas , Masami Hiramatsu , Mike Stunes , Joerg Roedel , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org List-Id: virtualization@lists.linuxfoundation.org On Thu, Jun 11, 2020 at 02:33:12PM -0500, Tom Lendacky wrote: > I don't think there is any guarantee that MONITOR/MWAIT would work within a > guest (I'd have to dig some more on that to get a definitive answer, but > probably not necessary to do). As you say, if KVM emulates it as a NOP, > there's no sense in exposing the GPA - make it a NOP in the handler. I just > need to poke some other hypervisor vendors and hear what they have to say. Okay, makes sense. I made monitor/mwait nops in the patch-set. Regards, Joerg