[v2] s390x/vfio-ap: hot plug/unplug vfio-ap device

[Qemu-devel] [PATCH v2 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device

Tony Krowiak posted 2 patches 5 years, 1 month ago

Diff against v3
Download series mbox

Test docker-clang@ubuntu failed

Test asan passed

Test docker-mingw@fedora passed

Test checkpatch passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/1550512800-9922-1-git-send-email-akrowiak@linux.ibm.com

Maintainers: Halil Pasic <pasic@linux.ibm.com>, Alex Williamson <alex.williamson@redhat.com>, David Hildenbrand <david@redhat.com>, Pierre Morel <pmorel@linux.ibm.com>, Tony Krowiak <akrowiak@linux.ibm.com>, Cornelia Huck <cohuck@redhat.com>, Richard Henderson <rth@twiddle.net>, Christian Borntraeger <borntraeger@de.ibm.com>

There is a newer version of this series

docs/vfio-ap.txt     | 58 +++++++++++++++++++++++++++++++++++++++++++++++-----
hw/s390x/ap-bridge.c | 12 ++++++++++-
hw/vfio/ap.c         |  2 +-
3 files changed, 65 insertions(+), 7 deletions(-)

Expand all Fold all

[Qemu-devel] [PATCH v2 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device

Posted by Tony Krowiak 5 years, 1 month ago

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(-)

-- 
2.7.4

Re: [Qemu-devel] [PATCH v2 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device

Posted by Tony Krowiak 5 years, 1 month ago

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(-)
>