From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, mjrosato@linux.ibm.com,
jjherne@linux.ibm.com, pasic@linux.ibm.com, fiuczy@linux.ibm.com,
thuth@redhat.com, farman@linux.ibm.com,
borntraeger@linux.ibm.com
Subject: Re: [PATCH 0/2] s390x/ap: fix hang when mdev attached to guest is removed
Date: Wed, 31 May 2023 08:40:10 -0400 [thread overview]
Message-ID: <24c0a1b0-4008-7f34-c33d-01e39721c1e4@linux.ibm.com> (raw)
In-Reply-To: <20230530225544.280031-1-akrowiak@linux.ibm.com>
The required kernel changes associated with the patch are here:
https://lore.kernel.org/linux-s390/20230530223538.279198-1-akrowiak@linux.ibm.com/
On 5/30/23 6:55 PM, Tony Krowiak wrote:
> When a user attempts to remove a vfio-ap mediated device attached to a
> guest, the operation hangs until the mdev's fd is closed by the guest
> (i.e., the guest is shut down). This patch series provides userspace
> (i.e., qemu) code to handle device unplug requests for AP. When notified
> that the mdev is being removed, the handler will unplug the device, thus
> avoiding the hang condition.
>
> Tony Krowiak (2):
> linux-headers: Update with vfio_ap IRQ index mapping
> s390x/ap: Wire up the device request notifier interface
>
> hw/vfio/ap.c | 113 +++++++++++++++++++++++++++++++++++++
> linux-headers/linux/vfio.h | 9 +++
> 2 files changed, 122 insertions(+)
>
prev parent reply other threads:[~2023-05-31 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 22:55 [PATCH 0/2] s390x/ap: fix hang when mdev attached to guest is removed Tony Krowiak
2023-05-30 22:55 ` [PATCH 1/2] linux-headers: Update with vfio_ap IRQ index mapping Tony Krowiak
2023-05-31 0:56 ` Matthew Rosato
2023-05-31 12:52 ` Anthony Krowiak
2023-05-31 13:07 ` Matthew Rosato
2023-05-31 13:12 ` Anthony Krowiak
2023-05-31 13:07 ` Cornelia Huck
2023-05-31 13:21 ` Anthony Krowiak
2023-05-30 22:55 ` [PATCH 2/2] s390x/ap: Wire up the device request notifier interface Tony Krowiak
2023-05-31 12:40 ` Anthony 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=24c0a1b0-4008-7f34-c33d-01e39721c1e4@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=fiuczy@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).