From: Anthony PERARD <anthony.perard@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Qemu-devel] [PATCH v4 15/18] xen: add a mechanism to automatically create XenDevice-s...
Date: Tue, 11 Dec 2018 16:50:30 +0000 [thread overview]
Message-ID: <20181211165030.GW18875@perard.uk.xensource.com> (raw)
In-Reply-To: <1544543862-9997-16-git-send-email-paul.durrant@citrix.com>
On Tue, Dec 11, 2018 at 03:57:39PM +0000, Paul Durrant wrote:
> ...that maintains compatibility with existing Xen toolstacks.
>
> Xen toolstacks instantiate PV backends by simply writing information into
> xenstore and expecting a backend implementation to be watching for this.
>
> This patch adds a new 'xen-backend' module to allow individual XenDevice
> implementations to register a creator function to be called when a tool-
> stack instantiates a new backend in this way.
>
> To support this it is also necessary to add new watchers into the XenBus
> implementation to handle enumeration of new backends and also destruction
> of XenDevice-s when the toolstack sets the backend 'online' key to 0.
>
> NOTE: This patch only adds the framework. A subsequent patch will add a
> creator function for xen-block devices.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
--
Anthony PERARD
next prev parent reply other threads:[~2018-12-11 16:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 15:57 [Qemu-devel] [PATCH v4 00/18] Xen PV backend 'qdevification' Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 01/18] xen: re-name XenDevice to XenLegacyDevice Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 02/18] xen: introduce new 'XenBus' and 'XenDevice' object hierarchy Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 03/18] xen: introduce 'xen-block', 'xen-disk' and 'xen-cdrom' Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 04/18] xen: create xenstore areas for XenDevice-s Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 05/18] xen: add xenstore watcher infrastructure Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 06/18] xen: add grant table interface for XenDevice-s Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 07/18] xen: add event channel " Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 08/18] xen: duplicate xen_disk.c as basis of dataplane/xen-block.c Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 09/18] xen: remove unnecessary code from dataplane/xen-block.c Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 10/18] xen: add header and build dataplane/xen-block.c Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 11/18] xen: remove 'XenBlkDev' and 'blkdev' names from dataplane/xen-block Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 12/18] xen: remove 'ioreq' struct/varable/field names from dataplane/xen-block.c Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 13/18] xen: purge 'blk' and 'ioreq' from function names in dataplane/xen-block.c Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 14/18] xen: add implementations of xen-block connect and disconnect functions Paul Durrant
2018-12-11 16:50 ` Anthony PERARD
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 15/18] xen: add a mechanism to automatically create XenDevice-s Paul Durrant
2018-12-11 16:50 ` Anthony PERARD [this message]
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 16/18] xen: automatically create XenBlockDevice-s Paul Durrant
2018-12-13 11:51 ` Kevin Wolf
2018-12-13 12:44 ` Paul Durrant
2018-12-13 15:08 ` Kevin Wolf
2018-12-14 14:50 ` Paul Durrant
2018-12-14 15:39 ` Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 17/18] MAINTAINERS: add myself as a Xen maintainer Paul Durrant
2018-12-11 15:57 ` [Qemu-devel] [PATCH v4 18/18] xen: remove the legacy 'xen_disk' backend Paul Durrant
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=20181211165030.GW18875@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--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).