From: Wei Liu <wei.liu2@citrix.com>
To: Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>
Cc: wei.liu2@citrix.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, embedded-pv-devel@lists.xenproject.org
Subject: Re: [PATCH RFC 0/6] Set of PV drivers used by production project
Date: Mon, 23 May 2016 12:40:35 +0100 [thread overview]
Message-ID: <20160523114035.GN31272@citrix.com> (raw)
In-Reply-To: <1463668655-16778-1-git-send-email-iurii.mykhalskyi@globallogic.com>
On Thu, May 19, 2016 at 05:37:29PM +0300, Iurii Mykhalskyi wrote:
> This patches introduce set of pv drivers interfaces.
> Drivers interfaces list:
> - PV RTC - real-time clock
> - PV TTY - interface for pv version for device controlled by
> via tty (e.g. GPS)
> - PV Audio - sound interface virtualization
> - PV DRM - direct rengering manager virtualization
> - PV RPMSG - remove procedure call interface, in our case
> used for playback codecs virtualization
>
> Iurii Mykhalskyi (2):
> libxl: implementation of PV rtc device interface
> libxl: implementation of PV tty device interface.
>
> Pavlo Suikov (4):
> libxl: implementation of PV audio device interface
> libxl: implementation of PV event device interface
> libxl: implementation of PV DRM device interface
> libxl: implementation of PV RPMSG device interface
>
> tools/libxl/libxl.c | 1781 +++++++++++++++++++++++++++++++++-
> tools/libxl/libxl.h | 102 ++
> tools/libxl/libxl_create.c | 214 +++-
> tools/libxl/libxl_device.c | 12 +
> tools/libxl/libxl_internal.c | 8 +
> tools/libxl/libxl_internal.h | 88 +-
> tools/libxl/libxl_types.idl | 131 +++
> tools/libxl/libxl_types_internal.idl | 6 +
> tools/libxl/libxl_utils.h | 19 +
> tools/libxl/xl.h | 18 +
> tools/libxl/xl_cmdimpl.c | 1035 +++++++++++++++++++-
> tools/libxl/xl_cmdtable.c | 95 ++
> 12 files changed, 3499 insertions(+), 10 deletions(-)
>
I've added this series to my list of things to look at, but it will
probably need to wait a bit before I can get to it.
Wei.
> --
> 2.8.2
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-23 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:37 [PATCH RFC 0/6] Set of PV drivers used by production project Iurii Mykhalskyi
2016-05-19 14:37 ` [PATCH RFC 1/6] libxl: implementation of PV rtc device interface Iurii Mykhalskyi
2016-05-23 16:45 ` Olaf Hering
2016-06-06 13:37 ` Wei Liu
2016-05-19 14:37 ` [PATCH RFC 2/6] libxl: implementation of PV audio " Iurii Mykhalskyi
2016-05-19 14:37 ` [PATCH RFC 3/6] libxl: implementation of PV tty " Iurii Mykhalskyi
2016-05-19 14:37 ` [PATCH RFC 4/6] libxl: implementation of PV event " Iurii Mykhalskyi
2016-05-19 14:37 ` [PATCH RFC 5/6] libxl: implementation of PV DRM " Iurii Mykhalskyi
2016-05-19 14:37 ` [PATCH RFC 6/6] libxl: implementation of PV RPMSG " Iurii Mykhalskyi
2016-05-19 17:52 ` [Embedded-pv-devel] [PATCH RFC 0/6] Set of PV drivers used by production project Meng Xu
2016-05-23 11:40 ` Wei Liu [this message]
2016-06-02 16:12 ` 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=20160523114035.GN31272@citrix.com \
--to=wei.liu2@citrix.com \
--cc=embedded-pv-devel@lists.xenproject.org \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=iurii.mykhalskyi@globallogic.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).