From: Eric Hankland <ehankland@google.com>
To: Jim Mattson <jmattson@google.com>, Peter Shier <pshier@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Eric Hankland <ehankland@google.com>
Subject: [kvm-unit-tests PATCH] x86: pmu: Test perfctr overflow after WRMSR on a running counter
Date: Fri, 21 Feb 2020 14:41:33 -0800 [thread overview]
Message-ID: <20200221224133.103377-1-ehankland@google.com> (raw)
Ensure that a WRMSR on a running counter will correctly update when the
counter should overflow (similar to the existing overflow test case but
with the counter being written to while it is running).
Signed-off-by: Eric Hankland <ehankland@google.com>
---
x86/pmu.c | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/x86/pmu.c b/x86/pmu.c
index c8096b8..f45621a 100644
--- a/x86/pmu.c
+++ b/x86/pmu.c
@@ -422,17 +422,34 @@ static void check_rdpmc(void)
static void check_running_counter_wrmsr(void)
{
+ uint64_t status;
pmu_counter_t evt = {
.ctr = MSR_IA32_PERFCTR0,
.config = EVNTSEL_OS | EVNTSEL_USR | gp_events[1].unit_sel,
.count = 0,
};
+ report_prefix_push("running counter wrmsr");
+
start_event(&evt);
loop();
wrmsr(MSR_IA32_PERFCTR0, 0);
stop_event(&evt);
- report(evt.count < gp_events[1].min, "running counter wrmsr");
+ report(evt.count < gp_events[1].min, "cntr");
+
+ /* clear status before overflow test */
+ wrmsr(MSR_CORE_PERF_GLOBAL_OVF_CTRL,
+ rdmsr(MSR_CORE_PERF_GLOBAL_STATUS));
+
+ evt.count = 0;
+ start_event(&evt);
+ wrmsr(MSR_IA32_PERFCTR0, -1);
+ loop();
+ stop_event(&evt);
+ status = rdmsr(MSR_CORE_PERF_GLOBAL_STATUS);
+ report(status & 1, "status");
+
+ report_prefix_pop();
}
int main(int ac, char **av)
reply other threads:[~2020-02-21 22:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200221224133.103377-1-ehankland@google.com \
--to=ehankland@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pshier@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®