Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5529655yba; Mon, 13 May 2019 12:29:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqwGqJVZxE4k5JfWOk73VpsbP8qHEYBVNt9rq3IpT27qRd+463ZXLhYB1Fr70LPutgQr6cos X-Received: by 2002:a62:6f02:: with SMTP id k2mr36728126pfc.136.1557775740263; Mon, 13 May 2019 12:29:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557775740; cv=none; d=google.com; s=arc-20160816; b=YoGdau1OOyYyiq2hhCCERvIG/HHGwa08bXLyVKUQCCEkHWpsbkvS0CU6tqLqVKvzws CyMQRB2UEa/UuMLhROka5r/438DuW2KQCw5LNAcwiMWvlpsMl/mBQMMO8JbWD08CIN2V gctGVOx5mVRAO8Up5TcDpYK1dDkbNGmVhkDsHHbjXYfINZmf/Lj08BgNtB6x+ugrUKGj fKs3Os50hJc9ktw5dLjkGRk21LKP7vxz7pJqKruhNHiBzHoDIWbcv6YEz/9QGyA8ubrI 0ei4TDQI/c+p1H3ws03GridLS1aQ9qdW/N5TMsVt1Ls3OGD7MF2lz/Wft/yKHY7JJBO2 VK2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=h8MNbl4vAuWZ92K25UarJLhpv5/nwdfbiimru367GCM=; b=s+FDIqRcXfC4QAD8m/FiYjZ4OjsGATycnnzCUBHsoIgGmfwm6gvJV370ktbNvDCGst RarjZ/wIcT9pY0rkh0Q/SUGHmdvhXXXcs0NCtH2BVGZHd7EBRMs27V+dm/aNJbhOSsgg On/bbiCRcU44wGbvPO/6FplGvDAOCanxOZSdG1eQKa+AhcyvLyIJkwau6RGUzumKvXyM 0+exs8hpGL14bLr5O8ZLM05AyZEvZolCvfB9LOpw5K6BhP+GNMJBhLpGr+a9+orw7jo3 UpQkD9QjdoQ0Xvw7oE5zDts6DMQZaDOjKP3mKcZzYYSkow165p3VhuOjpwMtJWT4Snnd Im2w== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b13si6582574plz.194.2019.05.13.12.28.44; Mon, 13 May 2019 12:29:00 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730828AbfEMQqc (ORCPT + 99 others); Mon, 13 May 2019 12:46:32 -0400 Received: from mga05.intel.com ([192.55.52.43]:43141 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728347AbfEMQqc (ORCPT ); Mon, 13 May 2019 12:46:32 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 May 2019 09:46:23 -0700 X-ExtLoop1: 1 Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.36]) by orsmga002.jf.intel.com with ESMTP; 13 May 2019 09:46:22 -0700 Date: Mon, 13 May 2019 09:46:22 -0700 From: Sean Christopherson To: Dave Hansen Cc: Alexandre Chartre , pbonzini@redhat.com, rkrcmar@redhat.com, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, dave.hansen@linux.intel.com, luto@kernel.org, peterz@infradead.org, kvm@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, konrad.wilk@oracle.com, jan.setjeeilers@oracle.com, liran.alon@oracle.com, jwadams@google.com Subject: Re: [RFC KVM 19/27] kvm/isolation: initialize the KVM page table with core mappings Message-ID: <20190513164622.GC28561@linux.intel.com> References: <1557758315-12667-1-git-send-email-alexandre.chartre@oracle.com> <1557758315-12667-20-git-send-email-alexandre.chartre@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 13, 2019 at 08:50:19AM -0700, Dave Hansen wrote: > I seem to remember that the KVM VMENTRY/VMEXIT context is very special. > Interrupts (and even NMIs?) are disabled. Would it be feasible to do > the switching in there so that we never even *get* interrupts in the KVM > context? NMIs are enabled on VMX's VM-Exit. On SVM, NMIs are blocked on exit until STGI is executed.