Date:   Wed, 15 Feb 2023 07:17:13 -0800
In-Reply-To: <73545081-0d82-fce6-43f0-c50aee9416cb@gmail.com>
Mime-Version: 1.0
References: <20230210003148.2646712-1-seanjc@google.com> <20230210003148.2646712-8-seanjc@google.com>
 <73545081-0d82-fce6-43f0-c50aee9416cb@gmail.com>
Message-ID: <Y+z2+5HPTRAa7+5i@google.com>
Subject: Re: [PATCH v2 07/21] KVM: x86/pmu: Zero out LBR capabilities during
 PMU refresh
From:   Sean Christopherson <seanjc@google.com>
To:     Like Xu <like.xu.linux@gmail.com>
Cc:     kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
        Paolo Bonzini <pbonzini@redhat.com>
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

On Wed, Feb 15, 2023, Like Xu wrote:
> On 10/2/2023 8:31 am, Sean Christopherson wrote:
> > Note, this is a very theoretical bug, there is no known use case where a
> > VMM would deliberately enable the vPMU via KVM_SET_CPUID2, and then later
> > disable the vPMU.
> 
> That's why we're getting more and more comfortable with selftests
> and fuzz testing on KVM interfaces. So is there a test for this ?

Yep, last patch in the series, "KVM: selftests: Verify LBRs are disabled if vPMU
is disabled".