[XEN PATCH 0/7] dom0less PV drivers

Stefano Stabellini posted 7 patches 2 weeks, 3 days ago
Test gitlab-ci passed
Patches applied successfully (tree, apply log)
git fetch https://gitlab.com/xen-project/patchew/xen tags/patchew/alpine.DEB.2.22.394.2201071614090.2060010@ubuntu-linux-20-04-desktop
docs/misc/arm/device-tree/booting.txt |  18 +++
tools/helpers/Makefile                |  13 ++
tools/helpers/init-dom0less.c         | 263 ++++++++++++++++++++++++++++++++++
tools/include/xenstore.h              |   3 +-
tools/libs/light/libxl_dom.c          |   3 +-
tools/libs/store/xs.c                 |   8 +-
tools/python/xen/lowlevel/xs/xs.c     |   2 +-
tools/xenstore/xenstored_domain.c     |  15 +-
xen/arch/arm/domain_build.c           |  39 +++++
xen/arch/arm/include/asm/domain.h     |   2 +
xen/arch/arm/include/asm/kernel.h     |   3 +
xen/common/event_channel.c            |  49 ++++---
xen/common/kernel.c                   |   2 +
xen/include/public/features.h         |   6 +
xen/include/xen/event.h               |   3 +
15 files changed, 403 insertions(+), 26 deletions(-)
create mode 100644 tools/helpers/init-dom0less.c

[XEN PATCH 0/7] dom0less PV drivers

Posted by Stefano Stabellini 2 weeks, 3 days ago
Hi all,

Currently dom0less guests cannot use PV drivers because they don't have
access to xenstore. Also, the hypervisor node in device tree is missing
so they don't detect that they are running on Xen (thus, they don't try
to enable PV interfaces.)

This patch series enables dom0less guests (on ARM) to use PV drivers.

Instead of initializing xenstore immediately at boot, dom0less guests
get access to xenstore later. They delay the initialization until they
receive a notification via the xenstore event channel (which is
available at boot.)

An example workflow is as follows:
- all domains start in parallel, dom0less guests are immediately running
- when dom0 is up and running, the init-dom0less application is called
- dom0less guests receive the notification and initialize xenstore
- now xl network-attach/disk-attach works as expected for dom0less domUs

In terms of interfaces, the patch series introduces:
- a new feature flag XENFEAT_xenstore_late_init to signal that xenstore
  is going to be available later
- a new dom0less device tree option "xen,enhanced" (in the Xen device
  tree) to specify whether PV interfaces should be enabled/disabled for
  the dom0less guest

Cheers,

Stefano

Luca Miccio (6):
      xen: introduce XENFEAT_xenstore_late_init
      xen: introduce _evtchn_alloc_unbound
      tools: add a late_init argument to xs_introduce_domain
      xen/arm: configure dom0less domain for enabling xenstore after boot
      xenstored: do_introduce: handle the late_init case
      tools: add example application to initialize dom0less PV drivers

Stefano Stabellini (1):
      xen: introduce xen,enhanced dom0less property

 docs/misc/arm/device-tree/booting.txt |  18 +++
 tools/helpers/Makefile                |  13 ++
 tools/helpers/init-dom0less.c         | 263 ++++++++++++++++++++++++++++++++++
 tools/include/xenstore.h              |   3 +-
 tools/libs/light/libxl_dom.c          |   3 +-
 tools/libs/store/xs.c                 |   8 +-
 tools/python/xen/lowlevel/xs/xs.c     |   2 +-
 tools/xenstore/xenstored_domain.c     |  15 +-
 xen/arch/arm/domain_build.c           |  39 +++++
 xen/arch/arm/include/asm/domain.h     |   2 +
 xen/arch/arm/include/asm/kernel.h     |   3 +
 xen/common/event_channel.c            |  49 ++++---
 xen/common/kernel.c                   |   2 +
 xen/include/public/features.h         |   6 +
 xen/include/xen/event.h               |   3 +
 15 files changed, 403 insertions(+), 26 deletions(-)
 create mode 100644 tools/helpers/init-dom0less.c