From: Wei Huang <wei@redhat.com>
To: cov@codeaurora.org
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
kvmarm@lists.cs.columbia.edu, shannon.zhao@linaro.org,
alistair.francis@xilinx.com, croberts@codeaurora.org,
alindsay@codeaurora.org, drjones@redhat.com
Subject: [Qemu-devel] [kvm-unit-tests PATCH v11 0/3] ARM PMU tests
Date: Tue, 22 Nov 2016 12:29:11 -0600 [thread overview]
Message-ID: <1479839354-22061-1-git-send-email-wei@redhat.com> (raw)
Changes from v10:
* Change the name of loop test function to precise_instrs_loop()
* Minor comment fixes to measure_instrs() and to explain isb() in loop funcs
Note:
1) Current KVM code has bugs in handling PMCCFILTR write. A fix (see
below) is required for this unit testing code to work correctly under
KVM mode.
https://lists.cs.columbia.edu/pipermail/kvmarm/2016-November/022134.html.
Thanks,
-Wei
Christopher Covington (3):
arm: Add PMU test
arm: pmu: Check cycle count increases
arm: pmu: Add CPI checking
arm/Makefile.common | 3 +-
arm/pmu.c | 351 ++++++++++++++++++++++++++++++++++++++++++++++++++++
arm/unittests.cfg | 19 +++
3 files changed, 372 insertions(+), 1 deletion(-)
create mode 100644 arm/pmu.c
--
1.8.3.1
next reply other threads:[~2016-11-22 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 18:29 Wei Huang [this message]
2016-11-22 18:29 ` [Qemu-devel] [kvm-unit-tests PATCH v11 1/3] arm: Add PMU test Wei Huang
2016-11-23 13:16 ` Andre Przywara
2016-11-23 15:47 ` Wei Huang
2016-11-23 17:15 ` Andrew Jones
2016-11-24 4:41 ` Wei Huang
2016-11-25 12:32 ` Andre Przywara
2016-11-25 14:26 ` Andrew Jones
2016-11-25 14:39 ` Andre Przywara
2016-12-01 5:35 ` Wei Huang
2016-11-22 18:29 ` [Qemu-devel] [kvm-unit-tests PATCH v11 2/3] arm: pmu: Check cycle count increases Wei Huang
2016-11-22 18:29 ` [Qemu-devel] [kvm-unit-tests PATCH v11 3/3] arm: pmu: Add CPI checking Wei Huang
2016-11-23 17:16 ` Andrew Jones
2016-11-23 17:18 ` [Qemu-devel] [kvm-unit-tests PATCH v11 0/3] ARM PMU tests Andrew Jones
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=1479839354-22061-1-git-send-email-wei@redhat.com \
--to=wei@redhat.com \
--cc=alindsay@codeaurora.org \
--cc=alistair.francis@xilinx.com \
--cc=cov@codeaurora.org \
--cc=croberts@codeaurora.org \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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).