qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tony Krowiak <akrowiak@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, borntraeger@de.ibm.com, cohuck@redhat.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 v2 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device
Date: Mon, 18 Feb 2019 14:08:16 -0500	[thread overview]
Message-ID: <b712101f-49dd-0ba7-0e8e-f90e4c34dbee@linux.ibm.com> (raw)
In-Reply-To: <1550512800-9922-1-git-send-email-akrowiak@linux.ibm.com>

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

      parent reply	other threads:[~2019-02-18 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 17:59 [Qemu-devel] [PATCH v2 0/2] s390x/vfio-ap: hot plug/unplug vfio-ap device Tony Krowiak
2019-02-18 17:59 ` [Qemu-devel] [PATCH v2 1/2] s390x/vfio-ap: Implement hot plug/unplug of " Tony Krowiak
2019-02-18 18:00 ` [Qemu-devel] [PATCH v2 2/2] s390x/vfio-ap: document " Tony Krowiak
2019-02-18 19:08 ` Tony Krowiak [this message]

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=b712101f-49dd-0ba7-0e8e-f90e4c34dbee@linux.ibm.com \
    --to=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.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).