From: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH 1/4] tools/libxendevicemodel: introduce the new library
Date: Mon, 20 Feb 2017 15:14:27 +0000 [thread overview]
Message-ID: <a8f6cec93c7f48eba6cc275d75d523a3@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170220151200.tsdbkvg7s4pnfcrg@citrix.com>
> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@citrix.com]
> Sent: 20 February 2017 15:12
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: xen-devel@lists.xenproject.org; Ian Jackson <Ian.Jackson@citrix.com>;
> Wei Liu <wei.liu2@citrix.com>; Samuel Thibault <samuel.thibault@ens-
> lyon.org>
> Subject: Re: [PATCH 1/4] tools/libxendevicemodel: introduce the new library
>
> On Mon, Feb 20, 2017 at 03:07:32PM +0000, Wei Liu wrote:
> > On Fri, Feb 17, 2017 at 10:27:06AM +0000, Paul Durrant wrote:
> > > The new xendevicemodel library is intended to be used by all Xen device
> > > models such that the only hypercall that use will be the dm_op hypercall
> > > added by commit 524a98c2.
> > >
> > > This patch adds the boilerplate for the new library, with only open() and
> > > close() entry points, and calls to those from libxenctrl in preparation
> > > for the compat layer added by a subsequent patch.
> > >
> > > NOTE: After applying this patch libxenctrl will depend on
> libxendevicemodel
> > > and so patches [1] and [2] must be applied to qemu-xen-traditional
> > > and mini-os respectively.
>
> Forgot to say:
>
> > >
> > > [1] http://xenbits.xen.org/gitweb/?p=people/pauldu/qemu-xen-
> traditional.git;a=commit;h=a445da7e
>
> Need an ack from Ian.
>
> > > [2] http://xenbits.xen.org/gitweb/?p=people/pauldu/mini-
> os.git;a=commit;h=41c9f2ae
> > >
>
> Need an ack from Samuel
OK. I guess the right thing is to get those committed first and then move the tags in Config.mk on in the next version of this series?
Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-20 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 10:27 [PATCH 1/4] tools/libxendevicemodel: introduce the new library Paul Durrant
2017-02-17 10:27 ` [PATCH 2/4] tools/libxendevicemodel: extract functions and add a compat layer Paul Durrant
2017-02-20 15:09 ` Wei Liu
2017-02-20 15:15 ` Paul Durrant
2017-02-17 10:27 ` [PATCH 3/4] tools/libxendevicemodel: introduce a Linux-specific implementation Paul Durrant
2017-02-20 15:09 ` Wei Liu
2017-02-17 10:27 ` [PATCH 4/4] tools/libxendevicemodel: add a call to restrict the handle Paul Durrant
2017-02-20 15:09 ` Wei Liu
2017-02-20 15:07 ` [PATCH 1/4] tools/libxendevicemodel: introduce the new library Wei Liu
2017-02-20 15:11 ` Paul Durrant
2017-02-20 15:12 ` Wei Liu
2017-02-20 15:14 ` Paul Durrant [this message]
2017-02-20 15:20 ` Wei Liu
2017-02-21 21:59 ` Samuel Thibault
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=a8f6cec93c7f48eba6cc275d75d523a3@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=wei.liu2@citrix.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).