xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>, yu.c.zhang@linux.intel.com
Cc: andrew.cooper3@citrix.com, Wei Liu <wei.liu2@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: [DO NOT APPLY PATCH XTF 0/2] UMIP test case
Date: Thu, 2 Mar 2017 08:42:30 +0000	[thread overview]
Message-ID: <20170302084232.13339-1-wei.liu2@citrix.com> (raw)
In-Reply-To: <58B78497.3010208@linux.intel.com>

I wrote this long time ago before UMIP was merged.

Yu, since you asked, I might as well post it for your reference on how to
do it with XTF.

This series is not yet tested in any way.

Wei Liu (2):
  x86: add UMIP feature bit
  Add UMIP test

 include/arch/x86/processor.h         |   1 +
 include/xen/arch-x86/cpufeatureset.h |   1 +
 tests/umip/Makefile                  |   9 ++++
 tests/umip/main.c                    | 102 +++++++++++++++++++++++++++++++++++
 4 files changed, 113 insertions(+)
 create mode 100644 tests/umip/Makefile
 create mode 100644 tests/umip/main.c

-- 
2.11.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-03-02  8:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  2:33 About UMIP unit test Yu Zhang
2017-03-02  8:06 ` Andrew Cooper
2017-03-02  8:42 ` Wei Liu [this message]
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=20170302084232.13339-1-wei.liu2@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=yu.c.zhang@linux.intel.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;
as well as URLs for NNTP newsgroup(s).