[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH v5 0/9] Support for running secondary emulators

This patch series adds the ioreq server interface which I mentioned in
my talk at the Xen developer summit in Edinburgh at the end of last year.
The code is based on work originally done by Julien Grall but has been
re-written to allow existing versions of QEMU to work unmodified.

The code is available in my xen.git [1] repo on xenbits, under the 'savannah5'
branch, and I have also written a demo emulator to test the code, which can
be found in my demu.git [2] repo.

The series has been re-worked since v4. The modifications are now broken
down as follows:

Patch #1 is a bug-fix in code touched later on in the series.

Patch #2 is a pre-series tidy-up. No semantic change.

Patch #3 moves some code around to centralize use of the ioreq_t data

Patch #4 introduces the new hvm_ioreq_server structure.

Patch #5 defers creation of the ioreq server until something actually
reads one of the HVM parameters concerned with emulation.

Patch #6 makes the single ioreq server of previous patches into the
default ioreq server and introduces an API for creating secondary servers.

Patch #7 adds an enable/disable operation to the API for secondary servers
which makes sure that they cannot be active whilst their shared pages are
present in the guest's P2M.

Patch #8 adds makes handling bufferd ioreqs optional for secondary servers.
This saves a page of memory per server.

Patch #9 pulls the PCI hotplug controller emulation into Xen. This is
necessary to allow a secondary emulator to hotplug a PCI device into the VM.
The code implements the controller in the same way as upstream QEMU and thus
the variant of the DSDT ASL used for upstream QEMU is retained.

The demo emulator can simply be invoked from a shell and will hotplug its
device onto the PCI bus (and remove it again when it's killed). The emulated
device is not an awful lot of use at this stage - it appears as a SCSI
controller with one IO BAR and one MEM BAR and has no intrinsic
functionality... but then it is only supposed to be demo :-)


[1] http://xenbits.xen.org/gitweb/?p=people/pauldu/xen.git
[2] http://xenbits.xen.org/gitweb/?p=people/pauldu/demu.git

 - First non-RFC posting

 - Addressed comments from Jan Beulich

 - Addressed comments from Ian Campbell and George Dunlap
 - Series heavily re-worked, 2 patches added

 - One more patch added to separate out a bug-fix, as requested by
   Jan Beulich
 - Switched to using rangesets as suggested by Jan Beulich
 - Changed domain restore path as requested by Ian Campbell
 - Added documentation for new hypercalls and libxenctrl API as requested
   by Ian Campbell
 - Added handling of multi-byte GPE I/O as suggested by Jan Beulich

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.