Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5850961pxj; Wed, 23 Jun 2021 10:12:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzJLDBU+KXF27jWvThx9VFYmaq2ax/BIpDU3Tb7caxSrGTrbbdPH7tB+ZLGcxe7IfASe0LL X-Received: by 2002:a02:820f:: with SMTP id o15mr548189jag.139.1624468368628; Wed, 23 Jun 2021 10:12:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624468368; cv=none; d=google.com; s=arc-20160816; b=QNdXm//IaXDPSItk31EGRlyBRa8qcLPQGTmmoEzudiGme1zSINMi/tdjdytL+yVxyu xyeNEw4kztd66+Ocd+ZXuwwk9EAasLDj9jxi6PPyTtLkHDi2r+/VLgetJSPO9V3U5kRP XyMxWAfGIHWhFJJx1rPfZn15vInztQBCnOGiiefu7NlKcAwo+pNHcRCxX4vWAdzH43T6 IfGE5LVTd2iFUDIu/bxh2DpOiiuDayQdug/byA7Bh2w8MpqZcmeoVlmxiruW+lDCEKGL xllUgqtqcLPSB3EdmLheR6EnRsl44gdiSMVu8IYqJQ+QwAEOyUJtncSFsT0uR46KjwGz k2QQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=0HXfW00/ZiOTGZh8Pkhz1aco0hFAG0H/heQF1wGLg5k=; b=PEXZTU/rgX6lBa8UaHeIVdet0NSC6tDqK34NlN+KG+12cWjIQvbgoN++Y9k01Ubq5c SPbzEfJy+RNnHgmamEQvXSHXQlUET40y0wehVsQlsHQSmis6lvYbWsi7dTckeMvpHl1T vLHNWTTPNQz6N1TME37AnaGfRR6aXucbsTOFvEIaLMDES2xT1OXJqQaxFfLXjOuYZwva 0QCP0xgsc5BV6oUqNv6q0N/2CC+EZbnhdDm12F4QNXzyVzfzX4WG0xOm2qkEd5EmPQYn R8oNW1A9iz50zyuoHjG9AkwoPzA66HwJuP5NDiZTFiXLj0ls2zZ37XnuabYZv3X8yKk5 3OGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QE91AAGX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id e24si534958ios.25.2021.06.23.10.12.36; Wed, 23 Jun 2021 10:12:48 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QE91AAGX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S229900AbhFWROU (ORCPT + 99 others); Wed, 23 Jun 2021 13:14:20 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:28430 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229831AbhFWROT (ORCPT ); Wed, 23 Jun 2021 13:14:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1624468321; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0HXfW00/ZiOTGZh8Pkhz1aco0hFAG0H/heQF1wGLg5k=; b=QE91AAGXuqPdxGEQ3h8PqY/UT/vGDlb81P2ykNHVwt8Q+O9x1uweP26JG2SO3/lNeTWwHw x4Sn8xJi6x5+/AgVd5/1+WyLrjF/faCwm3SsLRh4CKYi5Cyr1sPoS/taW2Wz/IcXmET1W+ aCGu8TfyqzXqlk4bEs/6TEVQ1G1ssOk= Received: from mail-ej1-f69.google.com (mail-ej1-f69.google.com [209.85.218.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-354-B6ki8joqP9-49oaxFao0Ug-1; Wed, 23 Jun 2021 13:12:00 -0400 X-MC-Unique: B6ki8joqP9-49oaxFao0Ug-1 Received: by mail-ej1-f69.google.com with SMTP id lt4-20020a170906fa84b0290481535542e3so1227996ejb.18 for ; Wed, 23 Jun 2021 10:11:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0HXfW00/ZiOTGZh8Pkhz1aco0hFAG0H/heQF1wGLg5k=; b=REChPUxm/pyoF/YTYBR+aNpqCiG5w4lV80xxOBOmMGEkNG2g7t/eOqgJp8pLw2Qp8l ANS+juSdCe+0qK3gWuogJU0YW/XWroV37ZelEqcPY5UTro4UOfQ+iFXg8f5YFffyEpmo ANXpFiIsBY3UQsaQewaup3z6s39gfXnizMbsMv+mpnXLview77OFbw1CN+h8Kft1OoWD hpFzfqYmooZEkVWI8C7QHzTI0JY1hN7spzhpIogkls8HbraxVmZeeMIu1UfZ5rNaXzcl F0TdXmGgm9kU1Axq0eM6roziwJo5rTCpLdu2u0Jd9p5FQ1mbCCG3+Ww63l5AmkEaJF/l HEsQ== X-Gm-Message-State: AOAM533u/Mr7jgWyIcTVKmgjtZaz0vo+VwCmkml2BJAZIbk0HkmZAApt kUifGHqlq0QRhQIPRSOEUXg8l8WZKkYWYPrpII22mIWB/CW3aRBEr90OuwEqZN9Mo+M8mNd8ex1 JyunCaRA5kyuQx+Mqa+Ux5RpV X-Received: by 2002:aa7:ca0d:: with SMTP id y13mr1104291eds.374.1624468318933; Wed, 23 Jun 2021 10:11:58 -0700 (PDT) X-Received: by 2002:aa7:ca0d:: with SMTP id y13mr1104263eds.374.1624468318739; Wed, 23 Jun 2021 10:11:58 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id by1sm158365ejc.30.2021.06.23.10.11.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Jun 2021 10:11:58 -0700 (PDT) Subject: Re: [PATCH 16/54] KVM: x86/mmu: Drop smep_andnot_wp check from "uses NX" for shadow MMUs To: Sean Christopherson Cc: Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Yu Zhang , Maxim Levitsky References: <20210622175739.3610207-1-seanjc@google.com> <20210622175739.3610207-17-seanjc@google.com> From: Paolo Bonzini Message-ID: Date: Wed, 23 Jun 2021 19:11:57 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <20210622175739.3610207-17-seanjc@google.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22/06/21 19:57, Sean Christopherson wrote: > Drop the smep_andnot_wp role check from the "uses NX" calculation now > that all non-nested shadow MMUs treat NX as used via the !TDP check. > > The shadow MMU for nested NPT, which shares the helper, does not need to > deal with SMEP (or WP) as NPT walks are always "user" accesses and WP is > explicitly noted as being ignored: > > Table walks for guest page tables are always treated as user writes at > the nested page table level. > > A table walk for the guest page itself is always treated as a user > access at the nested page table level > > The host hCR0.WP bit is ignored under nested paging. > > Signed-off-by: Sean Christopherson > --- > arch/x86/kvm/mmu/mmu.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c > index 96c16a6e0044..ca7680d1ea24 100644 > --- a/arch/x86/kvm/mmu/mmu.c > +++ b/arch/x86/kvm/mmu/mmu.c > @@ -4223,8 +4223,7 @@ reset_shadow_zero_bits_mask(struct kvm_vcpu *vcpu, struct kvm_mmu *context) > * NX can be used by any non-nested shadow MMU to avoid having to reset > * MMU contexts. Note, KVM forces EFER.NX=1 when TDP is disabled. > */ > - bool uses_nx = context->nx || !tdp_enabled || > - context->mmu_role.base.smep_andnot_wp; > + bool uses_nx = context->nx || !tdp_enabled; > struct rsvd_bits_validate *shadow_zero_check; > int i; > > Good idea, but why not squash it into patch 2? Paolo