From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Subject: Re: [PATCH kvm-unit-tests 00/10] report is nice, use it more
Date: Fri, 12 Dec 2014 17:19:54 +0100 [thread overview]
Message-ID: <20141212161954.GA17674@hawk.usersys.redhat.com> (raw)
In-Reply-To: <1418400377-17388-1-git-send-email-drjones@redhat.com>
On Fri, Dec 12, 2014 at 05:06:07PM +0100, Andrew Jones wrote:
> This series applies report() to more x86 unit tests. It also
> cleans up some uses of it in vmx_tests. Finally, it also
> introduces report prefix support, and applies that a few places.
> There should be no functional changes with this series, except of
> course the output formatting (which makes the churn debatable).
> Anyway, I believe this series helps us to start converging on a
> "standard" output format for all unit tests.
>
> I'm afraid I didn't test all the changes, as not all unit tests
> could run on my test machine.
> svm - didn't run
> xsave - didn't run 'have xsave' tests
> asyncpf - is commented out of unittests.cfg,
> and I didn't uncomment it out
> pmu - didn't run
>
> (I probably should add a bunch of kvm-unit-tests contributors to
> the CC in order to alert them that I'm touching their unit tests,
> but I don't think this series warrants all the git blaming, so
> I'm not adding anybody at all :-)
Forgot to mention that these patches are available here
https://github.com/rhdrjones/kvm-unit-tests/tree/more-report
>
>
> Andrew Jones (10):
> x86: hypercall: add missing report_summary
> x86: pmu: report takes a fmt
> x86: vmx: better use of report
> x86: tsc_adjust: use report
> x86: svm: use report
> x86: asyncpf: use report
> x86: xsave: use report
> report: add prefix support
> x86: use report prefixes
> arm: use report prefixes
>
> arm/selftest.c | 31 ++++-----
> lib/libcflat.h | 2 +
> lib/report.c | 22 ++++++
> lib/string.c | 17 +++++
> lib/string.h | 1 +
> x86/apic.c | 8 ++-
> x86/asyncpf.c | 15 ++--
> x86/hypercall.c | 2 +-
> x86/pmu.c | 28 +++++---
> x86/svm.c | 25 +++----
> x86/tsc_adjust.c | 44 ++++--------
> x86/vmx_tests.c | 204 +++++++++++++------------------------------------------
> x86/xsave.c | 150 +++++++++++++++-------------------------
> 13 files changed, 210 insertions(+), 339 deletions(-)
>
> --
> 1.9.3
>
next prev parent reply other threads:[~2014-12-12 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 16:06 [PATCH kvm-unit-tests 00/10] report is nice, use it more Andrew Jones
2014-12-12 16:06 ` [PATCH 01/10] x86: hypercall: add missing report_summary Andrew Jones
2014-12-12 16:06 ` [PATCH 02/10] x86: pmu: report takes a fmt Andrew Jones
2014-12-15 15:03 ` Paolo Bonzini
2014-12-15 15:03 ` Paolo Bonzini
2014-12-12 16:06 ` [PATCH 03/10] x86: vmx: better use of report Andrew Jones
2014-12-12 16:06 ` [PATCH 04/10] x86: tsc_adjust: use report Andrew Jones
2014-12-12 16:06 ` [PATCH 05/10] x86: svm: " Andrew Jones
2014-12-12 16:06 ` [PATCH 06/10] x86: asyncpf: " Andrew Jones
2014-12-12 16:06 ` [PATCH 07/10] x86: xsave: " Andrew Jones
2014-12-12 16:06 ` [PATCH 08/10] report: add prefix support Andrew Jones
2014-12-12 16:06 ` [PATCH 09/10] x86: use report prefixes Andrew Jones
2014-12-12 16:06 ` [PATCH 10/10] arm: " Andrew Jones
2014-12-12 16:19 ` Andrew Jones [this message]
2014-12-15 15:11 ` [PATCH kvm-unit-tests 00/10] report is nice, use it more Paolo Bonzini
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=20141212161954.GA17674@hawk.usersys.redhat.com \
--to=drjones@redhat.com \
--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 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.