Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1669953pxb; Sat, 16 Oct 2021 16:33:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwLkL6rQzWxfiPwl/nDhUZWr5qs6QjlRlDGCdgFhSCmptnfrhuQoSOHMZt0Fhn2jZ7VxuHV X-Received: by 2002:a17:906:1c04:: with SMTP id k4mr18506634ejg.279.1634427232165; Sat, 16 Oct 2021 16:33:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634427232; cv=none; d=google.com; s=arc-20160816; b=NIebiI0z/DZ0JXNyCZpTK4LlXIBj4A7P6VU4mzgimtMHiw16kVpM0PwIWsgEb8zipx aagRFVe7tEckYVy7B6FI4+WPf9ux4Os5C2xHzIyors1yodrMeKLZJGzn59OH6DEBHAkY WE1vfOs/9LOBchlpIabj+7/v3impjH3M6QV8C+BegygXMM4Esz1pJ1zXsQY3V4Ugqwmz ILPCN7Q2w89Kx5hnkZrCp428CaLCDVTasRj85pWPCcsAxEPDZkMYD385ixUILD0IAqZr 7vamlyrOqO8hg6I7lMhMFcfdaL9dhkXfjeABbJE/q5DjS6n/2GY1uyQZxdUpJHKMqcTf wQSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=699f+9o27CaSy+d/5EA2EABTaD/xyiI7eDXQXNgUQcg=; b=gm473ljJFG18qH0FbIXoRzjU7hjmFqmwCYxhZ82JF30ku9E8Eo44qLejwpuch+rmIN LTGi/x2XvJYb5B3dU9lHoKe0F7T2/Rc5L/ZzQYC8Z9xLl3PWbRmnO2YgW3D3ggIzY/aa jmmnTHDQEqQKdsvc8X/7nlGf8Qng03COUuCscX7jO5IHwoTkiSkfXImwl5q6C+i04T/7 YX8o8gJZKeDHC6AfCFGhufMLvbSY68aKqsPJxtxc6DotMhFqlO12jwbPPANS4awEDjzL 2ymQsw410G36fqRwRCgThprd/VavjodLRtoW9BBPv/8ggzfqN1SnE1B+ZRE7Ogzud5b+ pkAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SwejX5+8; 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 lb3si15287053ejc.204.2021.10.16.16.33.28; Sat, 16 Oct 2021 16:33:52 -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=SwejX5+8; 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 S236039AbhJOQEX (ORCPT + 99 others); Fri, 15 Oct 2021 12:04:23 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:49597 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234675AbhJOQEW (ORCPT ); Fri, 15 Oct 2021 12:04:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634313735; 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=699f+9o27CaSy+d/5EA2EABTaD/xyiI7eDXQXNgUQcg=; b=SwejX5+8DLRpaUMfiPq4HBfg0grZft1zoDuRdDY2gaVXHuTkp4QPolJhmPAVsi4VswKqxU z4bWJ78LX/9ni3wkQUL2r6vwtg8zaO8xcofw1vGVWXtqJpAayUhyATdSDNgTd+t51jvfK4 xnlQsxzluyYQHq5GMwdJ+6JmlNcjO3k= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-161-jpRUnrjjMFCI1VVbAHAnmw-1; Fri, 15 Oct 2021 12:02:14 -0400 X-MC-Unique: jpRUnrjjMFCI1VVbAHAnmw-1 Received: by mail-ed1-f70.google.com with SMTP id cy14-20020a0564021c8e00b003db8c9a6e30so8667189edb.1 for ; Fri, 15 Oct 2021 09:02:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=699f+9o27CaSy+d/5EA2EABTaD/xyiI7eDXQXNgUQcg=; b=SLCChnmH73w3zNsyoK5yIJAI7g7dkzPPwEjRAr0oerFQEHg4G/blQHMoNuMIz4BiUG KM6i0zlpZzTVdrA/f/szc45MQQLubtpk+xi68d6VIfXQkuOyBkTidey5wCAjbnW3GkjG xHYlhvrKtRIQcKaUvGe0Qcs67kmkgN7TRNHin+1Dz0HNm5o65SM5ZM0t/QKuXol3+IMd cntG+JPz28cEOg4BMN4hPFtzFiCLCfkd+IM4v99De/n+bZ0lXUCb1lywXkvHqYR1QFgf fjdQ3JTK3Ij3r6xs7rNIy29q9FEArksxqpv4sG9qIUOIj2uhNuNeL3Fasnu1+nnYrNau sliA== X-Gm-Message-State: AOAM530mQtJvEj4DcTYFNPkpYuZNv93roL2p515A1/DEvAH3QUj5ICub hM2+DPrSl9+X48JiCKlGZFJbg4KSbtYmR22BfuPiPCajQ8l6b1TjV1CISenJ5vecaSXyAQ5kZiF dtCde0dAXBW4dLE999iozTX/o X-Received: by 2002:a05:6402:35d1:: with SMTP id z17mr19175816edc.174.1634313733073; Fri, 15 Oct 2021 09:02:13 -0700 (PDT) X-Received: by 2002:a05:6402:35d1:: with SMTP id z17mr19175792edc.174.1634313732847; Fri, 15 Oct 2021 09:02:12 -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 y22sm5566150edc.76.2021.10.15.09.02.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 15 Oct 2021 09:02:12 -0700 (PDT) Message-ID: Date: Fri, 15 Oct 2021 18:02:11 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 Subject: Re: [PATCH 0/2] KVM: X86: Don't reset mmu context when changing PGE or PCID Content-Language: en-US To: Lai Jiangshan , Lai Jiangshan , linux-kernel@vger.kernel.org Cc: Sean Christopherson , Vitaly Kuznetsov , kvm@vger.kernel.org References: <20210919024246.89230-1-jiangshanlai@gmail.com> <506c12c4-4a56-bcbf-a566-a3e75c0814aa@linux.alibaba.com> From: Paolo Bonzini In-Reply-To: <506c12c4-4a56-bcbf-a566-a3e75c0814aa@linux.alibaba.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/10/21 18:03, Lai Jiangshan wrote: > Ping > > On 2021/9/19 10:42, Lai Jiangshan wrote: >> From: Lai Jiangshan >> >> This patchset uses kvm_vcpu_flush_tlb_guest() instead of >> kvm_mmu_reset_context() >> when X86_CR4_PGE is changed or X86_CR4_PCIDE is changed 1->0. >> >> Neither X86_CR4_PGE nor X86_CR4_PCIDE participates in kvm_mmu_role, so >> kvm_mmu_reset_context() is not required to be invoked.  Only flushing tlb >> is required as SDM says. >> >> The patchset has nothing to do with performance, because the overheads of >> kvm_mmu_reset_context() and kvm_vcpu_flush_tlb_guest() are the same.  And >> even in the [near] future, kvm_vcpu_flush_tlb_guest() will be optimized, >> the code is not in the hot path. >> >> This patchset makes the code more clear when to reset the mmu context. >> And it makes KVM_MMU_CR4_ROLE_BITS consistent with kvm_mmu_role. >> >> Lai Jiangshan (2): >>    KVM: X86: Don't reset mmu context when X86_CR4_PCIDE 1->0 >>    KVM: X86: Don't reset mmu context when toggling X86_CR4_PGE >> >>   arch/x86/kvm/mmu.h | 5 ++--- >>   arch/x86/kvm/x86.c | 7 +++++-- >>   2 files changed, 7 insertions(+), 5 deletions(-) >> > Queued with kvm_make_request(KVM_REQ_TLB_FLUSH_GUEST, vcpu) replacement, thanks. Paolo