From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, qian.ouyang@intel.com
Subject: About UMIP unit test.
Date: Thu, 2 Mar 2017 10:33:59 +0800 [thread overview]
Message-ID: <58B78497.3010208@linux.intel.com> (raw)
Hi Jan,
Previously I saw your UMIP patches merged in xen, and we'd like to
try some unit test here in Intel. And I wonder do you have any unit test
code for this feature, or any suggestions? :)
Thanks
Yu
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-03-02 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 2:33 Yu Zhang [this message]
2017-03-02 8:06 ` About UMIP unit test Andrew Cooper
2017-03-02 8:42 ` [DO NOT APPLY PATCH XTF 0/2] UMIP test case Wei Liu
2017-03-02 8:42 ` [DO NOT APPLY PATCH XTF 1/2] x86: add UMIP feature bit Wei Liu
2017-03-02 8:42 ` [DO NOT APPLY PATCH XTF 2/2] Add UMIP test Wei Liu
2017-03-02 9:05 ` [DO NOT APPLY PATCH XTF 0/2] UMIP test case Andrew Cooper
2017-03-02 10:53 ` Wei Liu
2017-03-02 12:30 ` Yu Zhang
2017-03-02 12:39 ` 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=58B78497.3010208@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=qian.ouyang@intel.com \
--cc=xen-devel@lists.xenproject.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).