From: Don Slutz <dslutz@verizon.com>
To: xen-devel@lists.xen.org
Cc: Don Slutz <dslutz@verizon.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [RFC][PATCH v1 0/3] Optional unit test tools for VMware tools support
Date: Tue, 2 Sep 2014 08:07:17 -0400 [thread overview]
Message-ID: <1409659640-20615-1-git-send-email-dslutz@verizon.com> (raw)
As I was finishing up "Add limited support of VMware's hyper-call",
I noticed that there was no command line support to access the new
features. Do to timing I decided to not delay the patch set any
longer, but send it out with out these optional unit test tools.
Since you need "Add limited support of VMware's hyper-call" patch
before you can apply this, I made it an RFC.
Current plan is to include them as v3 of the "Xen VMware tools
support". I am posting them sooner in order to speed things along.
Don Slutz (3):
Add xen-hvm-param
Add xen-vmware-guestinfo
Add xen-list-vmware-guestinfo
.gitignore | 3 +
tools/misc/Makefile | 13 ++-
tools/misc/xen-hvm-param.c | 154 +++++++++++++++++++++++++++++++++
tools/misc/xen-list-vmware-guestinfo.c | 88 +++++++++++++++++++
tools/misc/xen-vmware-guestinfo.c | 97 +++++++++++++++++++++
5 files changed, 353 insertions(+), 2 deletions(-)
create mode 100644 tools/misc/xen-hvm-param.c
create mode 100644 tools/misc/xen-list-vmware-guestinfo.c
create mode 100644 tools/misc/xen-vmware-guestinfo.c
--
1.8.4
next reply other threads:[~2014-09-02 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 12:07 Don Slutz [this message]
2014-09-02 12:07 ` [RFC][PATCH v1 1/3] Add xen-hvm-param Don Slutz
2014-09-02 12:47 ` Andrew Cooper
2014-09-02 15:11 ` Don Slutz
2014-09-02 12:07 ` [RFC][PATCH v1 2/3] Add xen-vmware-guestinfo Don Slutz
2014-09-02 12:07 ` [RFC][PATCH v1 3/3] Add xen-list-vmware-guestinfo Don Slutz
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=1409659640-20615-1-git-send-email-dslutz@verizon.com \
--to=dslutz@verizon.com \
--cc=stefano.stabellini@eu.citrix.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).