Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp950529ybb; Wed, 8 Apr 2020 13:11:43 -0700 (PDT) X-Google-Smtp-Source: APiQypL3MknfOBXNX/HcqALUlPSQB9WHC9TcJ4Vy4KvOz9xXIMjN6pJAsaWjspaytb2D3cN21xC5 X-Received: by 2002:a05:6830:1495:: with SMTP id s21mr7528934otq.35.1586376702976; Wed, 08 Apr 2020 13:11:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586376702; cv=none; d=google.com; s=arc-20160816; b=MpLBoJ7byJ4vHVYGuC2l4eWHhIr9HSMg3GRzrRcfhVRgg7QZHS0IKZmSTxEuJPnIm4 1+7NMI8bTmbJpnxoQga+DKfBL4qpMb94TvWeb2GCtIyJpFNQRhygCYCnAxScyVT6Fv2f DW2XUOnAT9z0x1mF5ROGu6w6I2pRhvAj83ClBLFDZfI4ddbhr03JLCtWQzvVvG/jHBzn Dys88Yx8VROpzzZxXuirkutSMeLDVEJ422FPjrqV41qf7Diuuzt/WA0Jjck44q3caWaA OQOHgSPEB2nrB1JSyGz6av3g/t6EQn0f8IJLlQn6xDPDIO7yr5Cj92qgyCA5NIOJb6Hu FyRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=hqTq2Wy3TNDTzfSsOcRzLQkDhw37DQsS+GCpZMUDZFo=; b=0TDUEMGOBk3kGaBwCyxk6Mbdfu89Sl3ii+ArMPtarYE5A4Xle3+Hyi9Ck+vwi4NYqb /21GwWI7MusBHvbdqEod15y7vr9EOhL+HhC/cFdyIqhIVYUbLTxMvTNWER5L/y53tvof p082qeTgQ1EoMmu4BbjhowkgHxhqFPpx+hUIH7sxhw7Dor2ab3Un8ZyYWF+LrB3RoUf2 XwulO+29VOXS2dvrqEI3vyXreFbLa7eWp6F+Q9eSsghw+MpxmzW1OHYFf8FNRIes+lfH EQFaQ8+/YA/858E9iLTHhVLUFVu/pJJm/LLzrjTCsVZczvlx3noth4xkHiiPmLS/sUAl 6u3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eEPqwTCR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a128si1974096oob.19.2020.04.08.13.11.29; Wed, 08 Apr 2020 13:11:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eEPqwTCR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730749AbgDHSXt (ORCPT + 99 others); Wed, 8 Apr 2020 14:23:49 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:51764 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730743AbgDHSXs (ORCPT ); Wed, 8 Apr 2020 14:23:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586370227; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hqTq2Wy3TNDTzfSsOcRzLQkDhw37DQsS+GCpZMUDZFo=; b=eEPqwTCRBo1Et90qpZ2uWEcLfaRYwP9J7Lb7wybHtfxWpjJl0m+LbWyRvaNVooCCJTDhSq YZsYXsAcZlet3WKjLhj1yqRbx06EfUe8+cYPVRS1lNmPh/mQ5JgjlXSvFIiLglcnWYy2Vw ZticrKC+wqPv+q12vvvWv1aVzPDxKP8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-415-XsFltCapNOamuqjPPB_lXg-1; Wed, 08 Apr 2020 14:23:41 -0400 X-MC-Unique: XsFltCapNOamuqjPPB_lXg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E9ED88017F4; Wed, 8 Apr 2020 18:23:39 +0000 (UTC) Received: from horse.redhat.com (ovpn-115-85.rdu2.redhat.com [10.10.115.85]) by smtp.corp.redhat.com (Postfix) with ESMTP id AFCA09A253; Wed, 8 Apr 2020 18:23:39 +0000 (UTC) Received: by horse.redhat.com (Postfix, from userid 10451) id 169B92202B8; Wed, 8 Apr 2020 14:23:39 -0400 (EDT) Date: Wed, 8 Apr 2020 14:23:39 -0400 From: Vivek Goyal To: Andy Lutomirski Cc: Thomas Gleixner , Peter Zijlstra , Andy Lutomirski , Paolo Bonzini , LKML , X86 ML , kvm list , stable Subject: Re: [PATCH v2] x86/kvm: Disable KVM_ASYNC_PF_SEND_ALWAYS Message-ID: <20200408182339.GC93547@redhat.com> References: <877dyqkj3h.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 07, 2020 at 09:48:02PM -0700, Andy Lutomirski wrote: [..] > It would be nifty if the host also told the guest what the guest virtual address was if the host knows it. It will be good to know and send guest virtual address as well. While sending SIGBUS to guest user space, information about which access triggered SIGBUS will be useful. I thought GUEST_LINEAR_ADDRESS provides guest virtual address if EPT_VIOLATION_GLA_VALID bit is set. And it seems to work for my simple test case. But when I try to read intel SDM, section "27.2" VM exits, EPT violations, I am not so sure. Somebody who understands this better, can you please help me understand what exactly GUEST_LINEAR_ADDRESS is supposed to contain during EPT violation. I assumed it is guest virtual address and added a patch in my RFC patch series. https://lore.kernel.org/kvm/20200331194011.24834-3-vgoyal@redhat.com/ But I might have misunderstood it. Vivek