From: Sean Christopherson <seanjc@google.com>
To: bugzilla-daemon@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 218739] pmu_counters_test kvm-selftest fails with (count != NUM_INSNS_RETIRED)
Date: Tue, 28 May 2024 10:20:41 -0700 [thread overview]
Message-ID: <ZlYSaSsQ_7y9J6r0@google.com> (raw)
In-Reply-To: <bug-218739-28872-qwpXtkuBFd@https.bugzilla.kernel.org/>
On Mon, May 27, 2024, bugzilla-daemon@kernel.org wrote:
> I also see this test fail sometimes (once per hour or so of continuous running)
> and in my case it fails because 'count != 0' assert on
> INTEL_ARCH_LLC_MISSES_INDEX event and only for this event.
>
> The reason is IMHO, is that it is possible to have 0 LLC misses if the cache
> is large enough and code was run for enough iterations.
The test does CLFUSH{,OPT} on its future code sequence after enabling the counter.
In theory, that's should guarantee an LLC Miss.
Hmm, but this SDM blurb about speculative loads makes me think past me was wrong.
(that is, data can be speculatively loaded into a cache line just before, during,
or after the execution of a CLFLUSH instruction that references the cache line).
next prev parent reply other threads:[~2024-05-28 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 14:29 [Bug 218739] New: pmu_counters_test kvm-selftest fails with (count != NUM_INSNS_RETIRED) bugzilla-daemon
2024-04-23 0:21 ` [Bug 218739] " bugzilla-daemon
2024-05-27 18:19 ` bugzilla-daemon
2024-05-28 17:20 ` Sean Christopherson [this message]
2024-05-28 17:20 ` bugzilla-daemon
2024-06-10 19:22 ` bugzilla-daemon
2024-06-20 21:28 ` bugzilla-daemon
2024-06-20 21:35 ` bugzilla-daemon
2024-06-21 15:14 ` bugzilla-daemon
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=ZlYSaSsQ_7y9J6r0@google.com \
--to=seanjc@google.com \
--cc=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).