From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: Selftests changes for 6.14
Date: Tue, 21 Jan 2025 07:45:00 -0800 [thread overview]
Message-ID: <Z4_A_N0-DMPsT4Uq@google.com> (raw)
In-Reply-To: <CABgObfZkQ_r_QY=xREKN+EdoaMRqRjVmk5Fz7UgdDrj=kmU9tQ@mail.gmail.com>
On Mon, Jan 20, 2025, Paolo Bonzini wrote:
> On Fri, Jan 17, 2025 at 2:07 AM Sean Christopherson <seanjc@google.com> wrote:
> >
> > FYI, the "LLC references/misses" patch exposed a latent failure on SKX/CLX/CPL[*]
> > (who's brilliant idea was it to use "CPL" for a CPU code name on x86?). Dapeng
> > is following up with the uarch folks to understand what's going on. If -rc1 is
> > immiment and we don't have a fix, my plan is to have the test only assert that
> > the count is non-zero, and then go with a more precise fix if one arises.
>
> So based on the thread there is a root cause and fix---the test is
> just counting on an unrelated event.
Oh, yeah. Sorry, forgot to follow-up here.
next prev parent reply other threads:[~2025-01-21 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 1:07 [GIT PULL] KVM x86 pull requests for 6.14 Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: Memslots hardening/cleanups " Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: x86: Misc/main changes 6.14 Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: x86: MMU changes for 6.15 Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: Selftests changes for 6.14 Sean Christopherson
2025-01-20 11:45 ` Paolo Bonzini
2025-01-21 15:45 ` Sean Christopherson [this message]
2025-01-17 1:07 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: vcpu_array fixes and cleanups " Sean Christopherson
2025-01-17 1:07 ` [GIT PULL] KVM: x86: VMX change " Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z4_A_N0-DMPsT4Uq@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.