Message ID | 1550512800-9922-1-git-send-email-akrowiak@linux.ibm.com (mailing list archive) |
---|---|
Headers | show |
Series | s390x/vfio-ap: hot plug/unplug vfio-ap device | expand |
On 2/18/19 12:59 PM, Tony Krowiak wrote: PLEASE IGNORE THIS PATCH SERIES. A v3 VERSION IS FORTHCOMING. VERSION v2 has already been posted and reviewed. > This patch series introduces hot plug/unplug of a vfio-ap device. > > A vfio-ap device can be hot plugged only if: > > 1. The guest does not yet have a vfio-ap device (only one is allowed > per guest) > > 2. The guest was started with the following CPU model features enabled: > * ap=on > * apft=on > > To hot plug a vfio-ap device, the QEMU device_add function may be used: > > (qemu) device_add vfio-ap,sysfsdev=$path-to-mdev > > Where $path-to-mdev is the absolute path to the mediated matrix device > to be used to configure the guest's AP device matrix. > > A vfio-ap device can be hot unplugged only if: > > 1. The guest was started with a vfio-ap device configured for it: > > -device vfio-ap,sysfsdev=$path-to-mdev > > 2. The guest was started with the following CPU model features enabled: > * ap=on > > Tony Krowiak (2): > s390x/vfio-ap: Implement hot plug/unplug of vfio-ap device > s390x/vfio-ap: document hot plug/unplug of vfio-ap device > > docs/vfio-ap.txt | 58 +++++++++++++++++++++++++++++++++++++++++++++++----- > hw/s390x/ap-bridge.c | 12 ++++++++++- > hw/vfio/ap.c | 2 +- > 3 files changed, 65 insertions(+), 7 deletions(-) >