Design Sessions 2019

Branch management (related to CI v2)

See https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#00709

Build System gripes

See https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#00786

Further defences for speculative sidechannels

See https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#00832

Xen Toolstacks

At the moment, we have a binary xl, which can be run; and we have libxl, which links 
against libxc and various other libraries, which must match 100% the hypervisor version. 
We have python and partial golang bindings for some of these libraries, but these may 
break and need recompilation when upgrading to a new version of Xen. This session is 
to discuss what, if anything, to do as a result of this.

A couple of options:

Make a daemon which links against libxl and exposes that functionality in a 
backwards-compatible manner

Make the Xen ABI fully backwards compatible, so that upgrades to Xen will work with 
older libraries

See

• https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#00789
• https://hackmd.io/0vZaSrKBT2iKWzpVMxDVvQ

Xen Distros

See https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#00791

Live Updating Xen

See https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#00834

Virtio

There is an interest on Arm to support virtio on Xen. This would allow us to 
leverage existing PV protocols (e.g virgil 3d) and offering an easy way for 
users to migrate to Xen.

The topics expected to be discussed during the sessions are:

   - Transport to be used
   - How to prevent backend to access all the guest memory
   - Sketch a plan and potential contributors

For notes, see https://lists.xenproject.org/archives/html/xen-devel/2019-07/threads.html#01746