From: Cornelia Huck <cohuck@redhat.com>
To: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
borntraeger@de.ibm.com, david@redhat.com,
bjsdjshi@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
alifm@linux.vnet.ibm.com, mjrosato@linux.vnet.ibm.com,
jjherne@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com,
eskultet@redhat.com, berrange@redhat.com,
alex.williamson@redhat.com, eric.auger@redhat.com,
pbonzini@redhat.com, peter.maydell@linaro.org, agraf@suse.de,
rth@twiddle.net, Tony Krowiak <akrowiak@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v6 4/5] s390x/vfio: ap: Introduce VFIO AP device
Date: Wed, 4 Jul 2018 13:24:29 +0200 [thread overview]
Message-ID: <20180704132429.3444bd18.cohuck@redhat.com> (raw)
In-Reply-To: <1530312483-23864-5-git-send-email-akrowiak@linux.vnet.ibm.com>
On Fri, 29 Jun 2018 18:48:02 -0400
Tony Krowiak <akrowiak@linux.vnet.ibm.com> wrote:
> Introduces a VFIO based AP device. The device is defined via
> the QEMU command line by specifying:
>
> -device vfio-ap,sysfsdev=<path-to-mediated-matrix-device>
>
> There may be only one vfio-ap device configured for a guest.
>
> The mediated matrix device is created by the VFIO AP device
> driver by writing a UUID to a sysfs attribute file (see
> docs/vfio-ap.txt). The mediated matrix device will be named
> after the UUID. Symbolic links to the $uuid are created in
> many places, so the path to the mediated matrix device $uuid
> can be specified in any of the following ways:
>
> /sys/devices/vfio_ap/matrix/$uuid
> /sys/devices/vfio_ap/matrix/mdev_supported_types/vfio_ap-passthrough/devices/$uuid
> /sys/bus/mdev/devices/$uuid
> /sys/bus/mdev/drivers/vfio_mdev/$uuid
>
> When the vfio-ap device is realized, it acquires and opens the
> VFIO iommu group to which the mediated matrix device is
> bound. This causes a VFIO group notification event to be
> signaled. The vfio_ap device driver's group notification
> handler will get called at which time the device driver
> will configure the the AP devices to which the guest will
> be granted access.
>
> Signed-off-by: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
Nit: You may want to decide one address or the other :)
> ---
> MAINTAINERS | 1 +
> default-configs/s390x-softmmu.mak | 1 +
> hw/vfio/Makefile.objs | 1 +
> hw/vfio/ap.c | 183 +++++++++++++++++++++++++++++++++++++
> include/hw/vfio/vfio-common.h | 1 +
> 5 files changed, 187 insertions(+), 0 deletions(-)
> create mode 100644 hw/vfio/ap.c
No complaints about the code from me.
next prev parent reply other threads:[~2018-07-04 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 22:47 [Qemu-devel] [PATCH v6 0/5] s390x: vfio-ap: guest dedicated crypto adapters Tony Krowiak
2018-06-29 22:47 ` [Qemu-devel] [PATCH v6 1/5] linux-headers: linux header updates for AP support Tony Krowiak
2018-06-29 22:48 ` [Qemu-devel] [PATCH v6 2/5] s390x/cpumodel: Set up CPU model for AP device support Tony Krowiak
2018-06-29 22:48 ` [Qemu-devel] [PATCH v6 3/5] s390x/ap: base Adjunct Processor (AP) object model Tony Krowiak
2018-07-04 10:01 ` Cornelia Huck
2018-06-29 22:48 ` [Qemu-devel] [PATCH v6 4/5] s390x/vfio: ap: Introduce VFIO AP device Tony Krowiak
2018-07-04 11:24 ` Cornelia Huck [this message]
2018-07-13 13:21 ` Tony Krowiak
2018-06-29 22:48 ` [Qemu-devel] [PATCH v6 5/5] s390: doc: detailed specifications for AP virtualization Tony Krowiak
2018-07-02 1:54 ` [Qemu-devel] [PATCH v6 0/5] s390x: vfio-ap: guest dedicated crypto adapters no-reply
2018-08-07 22:41 ` Tony Krowiak
2018-08-08 7:34 ` Cornelia Huck
2018-08-09 16:02 ` 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=20180704132429.3444bd18.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=akrowiak@linux.ibm.com \
--cc=akrowiak@linux.vnet.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=eric.auger@redhat.com \
--cc=eskultet@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
/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).