From: Matthew Rosato <mjrosato@linux.ibm.com>
To: jgg@nvidia.com, joro@8bytes.org, alex.williamson@redhat.com
Cc: will@kernel.org, cohuck@redhat.com, borntraeger@linux.ibm.com,
schnelle@linux.ibm.com, gerald.schaefer@linux.ibm.com,
farman@linux.ibm.com, iommu@lists.linux-foundation.org,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/s390: tolerate repeat attach_dev calls
Date: Thu, 19 May 2022 14:30:23 -0400 [thread overview]
Message-ID: <c9b89cd9-081b-6f35-7076-02c20e26e172@linux.ibm.com> (raw)
In-Reply-To: <20220519182929.581898-1-mjrosato@linux.ibm.com>
On 5/19/22 2:29 PM, Matthew Rosato wrote:
> Since commit 0286300e6045 ("iommu: iommu_group_claim_dma_owner() must
> always assign a domain") s390-iommu will get called to allocate multiple
> unmanaged iommu domains for a vfio-pci device -- however the current
> s390-iommu logic tolerates only one. Recognize that multiple domains can
> be allocated and handle switching between DMA or different iommu domain
> tables during attach_dev.
>
> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
> ---
Tested in conjuction with
https://lore.kernel.org/kvm/0-v1-9cfc47edbcd4+13546-vfio_dma_owner_fix_jgg@nvidia.com/
Along with that patch, vfio{-pci,-ap,-ccw} on s390x for -next seem happy
again.
next prev parent reply other threads:[~2022-05-19 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 18:29 [PATCH] iommu/s390: tolerate repeat attach_dev calls Matthew Rosato
2022-05-19 18:30 ` Matthew Rosato [this message]
2022-05-19 22:58 ` Jason Gunthorpe
2022-05-20 7:57 ` Joerg Roedel
2022-05-20 10:30 ` Niklas Schnelle
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=c9b89cd9-081b-6f35-7076-02c20e26e172@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=will@kernel.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).