From: Halil Pasic <pasic@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: qemu-devel@nongnu.org, jjherne@linux.ibm.com,
peter.maydell@linaro.org, pasic@linux.vnet.ibm.com,
cohuck@redhat.com, mjrosato@linux.ibm.com, pmorel@linux.ibm.com,
david@redhat.com, alifm@linux.ibm.com,
alex.williamson@redhat.com, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, fiuczy@linux.ibm.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH] s390x/vfio-ap: Implement hot plug/unplug of vfio-ap device
Date: Wed, 9 Jan 2019 18:05:51 +0100 [thread overview]
Message-ID: <20190109180551.5976c1f4@oc2783563651> (raw)
In-Reply-To: <1546963310-17024-1-git-send-email-akrowiak@linux.ibm.com>
On Tue, 8 Jan 2019 11:01:50 -0500
Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> Introduces hot plug/unplug support for the vfio-ap device. Note that only one
> vfio-ap device can be attached to the ap-bus, so a vfio-ap device can only be
> hot plugged if the '-device vfio-ap,sysfsdev=$path_to_mdev' option is not
> specified on the QEMU command line.
>
> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
> Reviewed-by: Pierre Morel<pmorel@linux.ibm.com>
> Tested-by: Pierre Morel<pmorel@linux.ibm.com>
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
prev parent reply other threads:[~2019-01-09 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:01 [Qemu-devel] [PATCH] s390x/vfio-ap: Implement hot plug/unplug of vfio-ap device Tony Krowiak
2019-01-08 16:09 ` David Hildenbrand
2019-01-08 19:52 ` Tony Krowiak
2019-01-08 22:13 ` David Hildenbrand
2019-01-09 11:30 ` Cornelia Huck
2019-01-09 16:27 ` Tony Krowiak
2019-01-09 16:37 ` David Hildenbrand
2019-01-09 17:13 ` Halil Pasic
2019-01-09 17:28 ` David Hildenbrand
2019-01-10 16:22 ` Tony Krowiak
2019-01-14 14:16 ` Cornelia Huck
2019-01-28 19:27 ` Tony Krowiak
2019-01-08 16:14 ` Tony Krowiak
2019-01-09 17:05 ` Halil Pasic [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=20190109180551.5976c1f4@oc2783563651 \
--to=pasic@linux.ibm.com \
--cc=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=jjherne@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).