From mboxrd@z Thu Jan 1 00:00:00 1970 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69909C19F2D for ; Tue, 9 Aug 2022 14:50:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244372AbiHIOuE (ORCPT ); Tue, 9 Aug 2022 10:50:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36204 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230226AbiHIOt7 (ORCPT ); Tue, 9 Aug 2022 10:49:59 -0400 Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E098C1CB1C for ; Tue, 9 Aug 2022 07:49:58 -0700 (PDT) Received: by mail-pg1-x52f.google.com with SMTP id f65so11532767pgc.12 for ; Tue, 09 Aug 2022 07:49:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=pj/fEy+PbSOJfjnAmjWjp05xip889MBZsAYo8a+A09M=; b=CXaj2mo3edpOrrs/eGAixM+dbKdbKNrdKswMb3QFsqibFiHrd0zQLlivVeSMpb5NBU 0OVZyUfeaiDip8FhxSvA0JN1Yzd+S+tyOctSvkpgSfu9Ds7e2w75/lLCNX/2raMU34uI 9iH4h045wCfCNy4t6/RaDbw/ro1zUMhC0iRlwYXF0GmSlqXE5Hs3aQmq/roM38MjBGvg lbtcc7Y5VCBykGHk4du/nAWcH8yMISZwnCRlXN+FO2rKv8mXxe4EemIGzpExOQI7MV51 vUHtL/hcOUP4J4f33kPHXkvlSCsfhWSS1oXRy4/lXEBtkXwB28Yg13qi1O8dsEAgP+34 g1sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=pj/fEy+PbSOJfjnAmjWjp05xip889MBZsAYo8a+A09M=; b=hDH+5A6Veav+6/B37T6EQO6hvWp7FXwwudE60R3essqWxdvW+yVlSkuOQyB+yJv8f1 4I4G75JqD6i4/x9m9ryQgT2WrpvwFAmTPbosQkju+N3OFN99eQ2C49dew88JlwnQ29Bg KmLGG2uJSotRWyxFstDPaAoICmbfG+b4qLO2is3QIDv6VHeWbKV8dPOF4CPNDMBheWKN a+YCW34KzyvmfaG0dcAGPHKo4r9G8AGuDWySeaFsLHTQOLOxXdiJB4Kf15bGyyJWkNww 6dogdZxDKY7q2PnXNpniTdDbVbWZlOygQr+E0YCoxjI4f4byByB+0aMR5LP8uVUrUP5b tebA== X-Gm-Message-State: ACgBeo2rsaimbg8WSuGJ3nFCHHjBHL/i3hD4bZ5hLTyfdPHkfAWSnoUz zsVozeBaTIGkFOy3QDoT2mMNbA== X-Google-Smtp-Source: AA6agR5raAJf/FGY+7K6wm6kyAjMcdb6Lw1pH0tvolG9dm1dLZhHNnUyqda3L+Izobzyg/WjAqaY3w== X-Received: by 2002:a63:4d1a:0:b0:41b:d319:d8ad with SMTP id a26-20020a634d1a000000b0041bd319d8admr19737406pgb.613.1660056598253; Tue, 09 Aug 2022 07:49:58 -0700 (PDT) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id jb9-20020a170903258900b001709e3c755fsm5596792plb.230.2022.08.09.07.49.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Aug 2022 07:49:57 -0700 (PDT) Date: Tue, 9 Aug 2022 14:49:54 +0000 From: Sean Christopherson To: Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, David Matlack , Yan Zhao , Mingwei Zhang , Ben Gardon Subject: Re: [PATCH v3 8/8] KVM: x86/mmu: explicitly check nx_hugepage in disallowed_hugepage_adjust() Message-ID: References: <20220805230513.148869-1-seanjc@google.com> <20220805230513.148869-9-seanjc@google.com> <36634375-e7ee-e28e-20dd-9ab1ebdd8040@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36634375-e7ee-e28e-20dd-9ab1ebdd8040@redhat.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, Aug 09, 2022, Paolo Bonzini wrote: > On 8/6/22 01:05, Sean Christopherson wrote: > > !is_large_pte(spte)) { > > + u64 page_mask; > > + > > + /* > > + * Ensure nx_huge_page_disallowed is read after checking for a > > + * present shadow page. A different vCPU may be concurrently > > + * installing the shadow page if mmu_lock is held for read. > > + * Pairs with the smp_wmb() in kvm_tdp_mmu_map(). > > + */ > > + smp_rmb(); > > + > > + if (!spte_to_child_sp(spte)->nx_huge_page_disallowed) > > + return; > > + > > I wonder if the barrier shouldn't be simply in to_shadow_page(), i.e. always > assume in the TDP MMU code that sp->xyz is read after the SPTE that points > to that struct kvm_mmu_page. If we can get away with it, I'd prefer to rely on the READ_ONCE() in kvm_tdp_mmu_read_spte() and required ordering of: READ_ONCE() => PRESENT => spte_to_child_sp()