Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7B1D2C433EF for ; Thu, 18 Nov 2021 18:14:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 632BC613B1 for ; Thu, 18 Nov 2021 18:14:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232131AbhKRSRf (ORCPT ); Thu, 18 Nov 2021 13:17:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39932 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231194AbhKRSRe (ORCPT ); Thu, 18 Nov 2021 13:17:34 -0500 Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3AABEC06173E for ; Thu, 18 Nov 2021 10:14:34 -0800 (PST) Received: by mail-pg1-x52c.google.com with SMTP id b4so6105972pgh.10 for ; Thu, 18 Nov 2021 10:14:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=lbp4MqK4c4z46q/2aYIm+UQvoFvvxFhTS5B7WVrAEA8=; b=ZBJBE1l2bVWc31h1gSBYlaeKhfXICxNNZZh4GSHjPRpL/HcYekj89wSpDHqQ0PWapE p06o68QrvN7pgpY7AxFh7kOaRq3uoQeW808ZTUSvQJYFGgriMKP8pzqt9N7jhALjr6lv 9BF2eHpQJ+rZdd6q0LF9SugofO0pZ0osBfrse9ZPZoI6aVpgPpH8Uw/UdhUfL2XnsrgR W1EV1uUvDrZ2cN5S68b6Zth7hrY+35LNhU9K2HMa8LEJWpkz6+L4tMY7M9p32Aae09De 5BYE4VaXV+6oK1bsdTFVzezx7a+h35quyjqtKjRKR4JzrUvYUTZ5gqbKh/UgUT2az07o pVdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=lbp4MqK4c4z46q/2aYIm+UQvoFvvxFhTS5B7WVrAEA8=; b=08aN+VPIsG7gdvlGsDnz9Y+eOu2yFRYVjfNtBx7XM8oPFGMU3a2c41uEUSK2s6T56i ArJLXHfj/ckZ8HFol1h00Ej+hXv1JOY45mkvyFTx1BKLXezYJ+nZR3MAZxPqrmzmtx7W +J5w3riDNnWKvgFpwM+FB6Bt2jOntp63DKAh6jh3k+9bYNf/ft+Ea+BGnKEWEgHdpnya TZG/6eKaRoGspJom1sDknqxKoaDONaokRtqyyFUH7dGKP5GMGNNUUWPQaEPVCmD2lKIK Ght/Gv96xj5LqDZ9qHTQUt9FKl8bYVI7RYb6zarryXPqvHAkd4a9QbnkoKKz5Tx4lTJj iw3g== X-Gm-Message-State: AOAM531hJKFDLKmUwTVNTRZ5O0e/PbOQKvJ24DNmy3dtwlJoL5iVFWsS kgB9Ya24jmiX7JTB89B9jySZfQ== X-Google-Smtp-Source: ABdhPJwjDPgQSoqj/zhVHGckKLjTYkAZpZu+dwkqMC5y0WTkG3fcKlYNus6y0JPo9sIcu71qwcxclw== X-Received: by 2002:a05:6a00:cc8:b0:49f:c4a9:b9f1 with SMTP id b8-20020a056a000cc800b0049fc4a9b9f1mr16915645pfv.32.1637259273548; Thu, 18 Nov 2021 10:14:33 -0800 (PST) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id d2sm310276pfj.42.2021.11.18.10.14.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Nov 2021 10:14:33 -0800 (PST) Date: Thu, 18 Nov 2021 18:14:29 +0000 From: Sean Christopherson To: Paolo Bonzini Cc: Ben Gardon , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Peter Xu , Peter Shier , David Matlack , Mingwei Zhang , Yulei Zhang , Wanpeng Li , Xiao Guangrong , Kai Huang , Keqian Zhu , David Hildenbrand Subject: Re: [RFC 11/19] KVM: x86/mmu: Factor shadow_zero_check out of make_spte Message-ID: References: <20211110223010.1392399-1-bgardon@google.com> <20211110223010.1392399-12-bgardon@google.com> <12a5ad9a-c1c5-852c-5041-096d2c518f8c@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <12a5ad9a-c1c5-852c-5041-096d2c518f8c@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 18, 2021, Paolo Bonzini wrote: > On 11/18/21 19:02, Sean Christopherson wrote: > > > but that's not a great name because the former is used also when shadowing > > > EPT/NPT. I'm thinking of standardizing on "shadow" and "TDP" (it's not > > > perfect because of the 32-bit and tdp_mmu=0 cases, but it's a start). Maybe > > > even split parts of mmu.c out into shadow_mmu.c. > > But shadow is flat out wrong until EPT and NPT support is ripped out of the "legacy" > > MMU. > > Yeah, that's true. "full" MMU? :) Or we could just rip out non-nested TDP support from the legacy MMU and call it the shadow MMU :-)