From: Cornelia Huck <cohuck@redhat.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
borntraeger@de.ibm.com, david@redhat.com, pmorel@linux.ibm.com,
alifm@linux.ibm.com, mjrosato@linux.ibm.com, pasic@linux.ibm.com,
alex.williamson@redhat.com, fiuczy@linux.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device
Date: Mon, 25 Feb 2019 13:42:38 +0100 [thread overview]
Message-ID: <20190225134238.4ad9b951.cohuck@redhat.com> (raw)
In-Reply-To: <1550519397-25359-1-git-send-email-akrowiak@linux.ibm.com>
On Mon, 18 Feb 2019 14:49:55 -0500
Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> This patch series introduces hot plug/unplug of a vfio-ap device.
>
> 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 which AP resources to be used by the guest have been assigned.
>
> A vfio-ap device can be hot plugged only if:
>
> 1. A vfio-ap device has not been attached to the ap-bus (only one is
> allowed per guest) either via the QEMU command line or a prior hot
> plug action.
>
> 2. The guest was started with the CPU model feature for AP enabled
> (e.g., -cpu host,ap=on).
>
> To hot unplug a vfio-ap device, the QEMU device-del function may be used:
>
> (qemu) device_del vfio-ap,sysfsdev=$path-to-mdev
>
> Where $path-to-mdev is the absolute path to the mediated matrix device
> specified when the vfio-ap device was attached to the virtual machine's
> ap-bus.
>
> A vfio-ap device can be hot unplugged only if:
>
> 1. A vfio-ap device has been attached to the virtual machine's ap-abus
> either via the QEMU command line or a prior hot plug action.
>
> 2. The guest was started with the CPU model feature for AP enabled
> (e.g., -cpu host,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(-)
>
In the meantime, the signature of qbus_set_hotplug_handler() has
changed to take an Object instead of a DeviceState, but I just went
ahead and did that trivial change myself.
Thanks, applied.
next prev parent reply other threads:[~2019-02-25 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 19:49 [Qemu-devel] [PATCH v3 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device Tony Krowiak
2019-02-18 19:49 ` [Qemu-devel] [PATCH v3 1/2] s390x/vfio-ap: Implement hot plug/unplug of " Tony Krowiak
2019-02-18 19:49 ` [Qemu-devel] [PATCH v3 2/2] s390x/vfio-ap: document " Tony Krowiak
2019-02-20 15:51 ` Cornelia Huck
2019-02-21 16:26 ` Tony Krowiak
2019-02-21 16:32 ` Cornelia Huck
2019-03-11 14:36 ` Tony Krowiak
2019-02-25 12:42 ` Cornelia Huck [this message]
2019-03-11 14:37 ` [Qemu-devel] [PATCH v3 0/2] s390x/vfio-ap: hot plug/unplug " Tony Krowiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190225134238.4ad9b951.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=fiuczy@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).