From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mohit Gambhir <mohit.gambhir@oracle.com>, xen-devel@lists.xen.org
Cc: boris.ostrovsky@oracle.com
Subject: Re: [PATCH v3 0/2][XTF] xtf/vpmu VPMU tests
Date: Tue, 25 Apr 2017 19:50:06 +0100 [thread overview]
Message-ID: <af6f0f2d-c4e0-0b58-45db-f96084b2d2c7@citrix.com> (raw)
In-Reply-To: <20170424175430.395-1-mohit.gambhir@oracle.com>
On 24/04/17 18:54, Mohit Gambhir wrote:
> Mohit Gambhir (2):
> xtf/vpmu: Add Intel PMU MSR addresses
> xtf/vpmu: MSR read/write tests for VPMU
>
> arch/x86/include/arch/msr-index.h | 11 +
> tests/vpmu/Makefile | 9 +
> tests/vpmu/main.c | 504 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 524 insertions(+)
> create mode 100644 tests/vpmu/Makefile
> create mode 100644 tests/vpmu/main.c
>
Independently from the content of this series, how have you found the
XTF to use? Any issues or unexpected corner cases which can be improved?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-25 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 17:54 [PATCH v3 0/2][XTF] xtf/vpmu VPMU tests Mohit Gambhir
2017-04-24 17:54 ` [PATCH v3 1/2][XTF] xtf/vpmu: Add Intel PMU MSR addresses Mohit Gambhir
2017-04-25 8:36 ` Jan Beulich
2017-04-25 15:04 ` Mohit Gambhir
2017-04-25 15:24 ` Andrew Cooper
2017-04-25 17:46 ` Mohit Gambhir
2017-04-26 6:07 ` Jan Beulich
2017-04-26 8:02 ` Andrew Cooper
2017-04-24 17:54 ` [PATCH v3 2/2][XTF] xtf/vpmu: MSR read/write tests for VPMU Mohit Gambhir
2017-04-25 18:20 ` Andrew Cooper
2017-04-25 21:45 ` Mohit Gambhir
2017-05-03 20:41 ` Andrew Cooper
2017-05-04 21:13 ` Mohit Gambhir
2017-05-04 21:36 ` Mohit Gambhir
2017-04-25 18:50 ` Andrew Cooper [this message]
2017-04-28 19:35 ` [PATCH v3 0/2][XTF] xtf/vpmu VPMU tests Mohit Gambhir
2017-05-03 20:07 ` Andrew Cooper
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=af6f0f2d-c4e0-0b58-45db-f96084b2d2c7@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=mohit.gambhir@oracle.com \
--cc=xen-devel@lists.xen.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).