qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, borntraeger@de.ibm.com,
	cohuck@redhat.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,
	akrowiak@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v4 0/5] s390x: vfio-ap: guest dedicated crypto adapters
Date: Sun, 15 Apr 2018 15:07:19 -0400	[thread overview]
Message-ID: <1523819244-29954-1-git-send-email-akrowiak@linux.vnet.ibm.com> (raw)

This patch series is the QEMU counterpart to the KVM/kernel support for 
guest dedicated crypto adapters. The KVM/kernel model is built on the 
VFIO mediated device framework and provides the infrastructure for 
granting exclusive guest access to crypto devices installed on the linux 
host. This patch series introduces a new QEMU command line option, QEMU 
object model and CPU model features to exploit the KVM/kernel model.

See the detailed specifications for AP virtualization provided by this 
patch set in docs/vfio-ap.txt for a more complete discussion of the 
design introduced by this patch series.

Note: This series implements the minimal viable product (MVP) and does not
      provide support for hot plug/unplug, migration, or VSIE. The goal
      of the MVP model is to solidify a base upon which these additional 
      features will be built.

v3 => v4 Change log:
===================
* Made vfio-ap device unpluggable for now
* Renamed command line CPU model feature for QCI: qci=on -> apqci=on
* Removed call to KVM_S390_VM_CRYPTO_INTERPRET_AP ioctl - ioctl was 
  removed from kernel and AP instruction interpretation is set from the
  VFIO device driver
* Added check to ensure only one vfio-ap device can be configured per 
  guest
* Removed AP instruction interception handlers: AP instructions will be 
  interpreted by default if AP facilities are installed to handle the case
  where feature ap=on and no vfio-ap device is configured for the guest.

Tony Krowiak (5):
  linux-headers: linux header updates for AP support
  s390x/ap: base Adjunct Processor (AP) object
  s390x/cpumodel: Set up CPU model for AP device support
  s390x/vfio: ap: Introduce VFIO AP device
  s390: doc: detailed specifications for AP virtualization

 default-configs/s390x-softmmu.mak |    1 +
 docs/vfio-ap.txt                  |  649 +++++++++++++++++++++++++++++++++++++
 hw/s390x/Makefile.objs            |    1 +
 hw/s390x/ap-device.c              |   39 +++
 hw/vfio/Makefile.objs             |    1 +
 hw/vfio/ap.c                      |  191 +++++++++++
 include/hw/s390x/ap-device.h      |   38 +++
 include/hw/vfio/vfio-common.h     |    1 +
 linux-headers/asm-s390/kvm.h      |    2 +
 linux-headers/linux/vfio.h        |    2 +
 target/s390x/cpu_features.c       |    3 +
 target/s390x/cpu_features_def.h   |    3 +
 target/s390x/cpu_models.c         |    2 +
 target/s390x/gen-features.c       |    3 +
 target/s390x/kvm.c                |    1 +
 ui/keycodemapdb                   |    2 +-
 16 files changed, 938 insertions(+), 1 deletions(-)
 create mode 100644 docs/vfio-ap.txt
 create mode 100644 hw/s390x/ap-device.c
 create mode 100644 hw/vfio/ap.c
 create mode 100644 include/hw/s390x/ap-device.h

             reply	other threads:[~2018-04-15 19:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-15 19:07 Tony Krowiak [this message]
2018-04-15 19:07 ` [Qemu-devel] [PATCH v4 1/5] linux-headers: linux header updates for AP support Tony Krowiak
2018-04-15 19:07 ` [Qemu-devel] [PATCH v4 2/5] s390x/ap: base Adjunct Processor (AP) object Tony Krowiak
2018-04-18  9:16   ` Pierre Morel
2018-04-22 15:39     ` Tony Krowiak
2018-04-15 19:07 ` [Qemu-devel] [PATCH v4 3/5] s390x/cpumodel: Set up CPU model for AP device support Tony Krowiak
2018-04-16 15:44   ` David Hildenbrand
2018-04-17 18:20     ` Tony Krowiak
2018-04-17 18:21     ` Christian Borntraeger
2018-04-18  7:40       ` Cornelia Huck
2018-04-18  8:59         ` David Hildenbrand
2018-04-22 15:41           ` Tony Krowiak
2018-05-03 14:54           ` Tony Krowiak
2018-04-22 15:40         ` Tony Krowiak
2018-04-18 10:55   ` Halil Pasic
2018-04-18 11:03     ` David Hildenbrand
2018-04-18 11:50       ` Pierre Morel
2018-04-22 15:52       ` Tony Krowiak
2018-04-22 15:43     ` Tony Krowiak
2018-04-22 16:01       ` Halil Pasic
2018-04-22 16:15         ` Tony Krowiak
2018-05-08 10:46         ` Tony Krowiak
2018-04-22 15:52     ` Tony Krowiak
2018-04-22 16:03       ` Halil Pasic
2018-04-15 19:07 ` [Qemu-devel] [PATCH v4 4/5] s390x/vfio: ap: Introduce VFIO AP device Tony Krowiak
2018-04-18  9:11   ` Pierre Morel
2018-04-22 15:55     ` Tony Krowiak
2018-04-19 12:03   ` Cornelia Huck
2018-04-22 16:05     ` Tony Krowiak
2018-04-23  7:00       ` Cornelia Huck
2018-04-26 14:50         ` Tony Krowiak
2018-04-15 19:07 ` [Qemu-devel] [PATCH v4 5/5] s390: doc: detailed specifications for AP virtualization Tony Krowiak
2018-04-15 19:14 ` [Qemu-devel] [PATCH v4 0/5] s390x: vfio-ap: guest dedicated crypto adapters no-reply
2018-04-19 11:51 ` Cornelia Huck
2018-04-22 16:17   ` Tony Krowiak
2018-04-23  7:01     ` Cornelia Huck

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=1523819244-29954-1-git-send-email-akrowiak@linux.vnet.ibm.com \
    --to=akrowiak@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --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=cohuck@redhat.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).