From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xen.org
Cc: Juergen Gross <jgross@suse.com>,
wei.liu2@citrix.com, ian.jackson@eu.citrix.com
Subject: [PATCH 0/6] libxl: extend device type framework
Date: Tue, 12 Jul 2016 17:30:38 +0200 [thread overview]
Message-ID: <1468337444-24108-1-git-send-email-jgross@suse.com> (raw)
Extend the device type framework in libxl to cover more functions in a
generic way. This allows to have all functionality of a specific device
type in just one source file instead of spreading it via multiple files
and have functions to deal with multiple device types in a similar way.
Some patches of this series can be regarded as RFC, as having e.g. all
nic related functions in one file is a matter of taste. I haven't
marked the patches as RFC as they are completely tested and I believe
the result is an improvement over current status.
Juergen Gross (6):
libxl: add "merge" function to generic device type support
libxl: add "pv device mode needed" support to device type framework
libxl: move library pvusb specific code into libxl_pvusb.c
libxl: split libxl vtpm code into one source
libxl: add config update callback to device type framework
libxl: move common nic stuff into one source
tools/libxl/Makefile | 1 +
tools/libxl/libxl.c | 930 ++++++-------------------------------------
tools/libxl/libxl_create.c | 35 +-
tools/libxl/libxl_dm.c | 31 +-
tools/libxl/libxl_internal.c | 21 +-
tools/libxl/libxl_internal.h | 77 ++--
tools/libxl/libxl_nic.c | 554 ++++++++++++++++++++++++++
tools/libxl/libxl_pci.c | 8 +-
tools/libxl/libxl_pvusb.c | 42 +-
tools/libxl/libxl_utils.c | 96 -----
tools/libxl/libxl_vtpm.c | 380 ++++++++++++++++++
11 files changed, 1192 insertions(+), 983 deletions(-)
create mode 100644 tools/libxl/libxl_nic.c
create mode 100644 tools/libxl/libxl_vtpm.c
--
2.6.6
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-07-12 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 15:30 Juergen Gross [this message]
2016-07-12 15:30 ` [PATCH 1/6] libxl: add "merge" function to generic device type support Juergen Gross
2016-07-25 10:45 ` Wei Liu
2017-01-19 16:14 ` Olaf Hering
2017-01-19 16:19 ` Wei Liu
2017-01-19 16:51 ` Juergen Gross
2016-07-12 15:30 ` [PATCH 2/6] libxl: add "pv device mode needed" support to device type framework Juergen Gross
2016-07-25 10:46 ` Wei Liu
2016-07-12 15:30 ` [PATCH 3/6] libxl: move library pvusb specific code into libxl_pvusb.c Juergen Gross
2016-07-25 10:46 ` Wei Liu
2016-07-12 15:30 ` [PATCH 4/6] libxl: split libxl vtpm code into one source Juergen Gross
2016-07-25 10:46 ` Wei Liu
2016-07-12 15:30 ` [PATCH 5/6] libxl: add config update callback to device type framework Juergen Gross
2016-07-25 10:46 ` Wei Liu
2016-07-12 15:30 ` [PATCH 6/6] libxl: move common nic stuff into one source Juergen Gross
2016-07-25 10:46 ` Wei Liu
2016-07-21 13:12 ` [PATCH 0/6] libxl: extend device type framework Juergen Gross
2016-07-27 11:45 ` Wei Liu
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=1468337444-24108-1-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@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).