From: Jason Gunthorpe <jgg@ziepe.ca>
To: Timothy Pearson <tpearson@raptorengineering.com>
Cc: jroedel <jroedel@suse.de>, gbatra <gbatra@linux.vnet.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
npiggin <npiggin@gmail.com>,
aneesh kumar <aneesh.kumar@kernel.org>,
iommu <iommu@lists.linux.dev>, bgray <bgray@linux.ibm.com>,
naveen n rao <naveen.n.rao@linux.ibm.com>,
vaibhav <vaibhav@linux.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, aik <aik@amd.com>
Subject: Re: [PATCH 1/2] powerpc: iommu: Bring back table group release_ownership() call
Date: Fri, 26 Jan 2024 11:44:27 -0400 [thread overview]
Message-ID: <20240126154427.GB50608@ziepe.ca> (raw)
In-Reply-To: <1453449220.10126352.1706283596477.JavaMail.zimbra@raptorengineeringinc.com>
On Fri, Jan 26, 2024 at 09:39:56AM -0600, Timothy Pearson wrote:
> > Just forget about the weird KVM and SPAPR stuff, leave it under the
> > kconfig of the old code and nobody will run it. Almost nobody already
> > runs it, apparently.
>
> We actually use QEMU/KVM/VFIO extensively at Raptor, so need the
> support and need it to be performant...
I wonder if you alone are the "almost" :)
The KVM entanglement was hairy and scary. I never did figure out what
was really going on there. Maybe you don't need all of it and can be
successful with a more typical iommu working model?
Suggest to tackle it after getting the first parts done.
Jason
next prev parent reply other threads:[~2024-01-26 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 12:08 [PATCH 0/2] powerpc: iommu: Fix the vfio-pci bind and unbind issues Shivaprasad G Bhat
2024-01-25 12:08 ` [PATCH 1/2] powerpc: iommu: Bring back table group release_ownership() call Shivaprasad G Bhat
2024-01-25 15:50 ` Jason Gunthorpe
2024-01-26 15:13 ` Shivaprasad G Bhat
2024-01-26 15:17 ` Jason Gunthorpe
2024-01-26 15:29 ` Timothy Pearson
2024-01-26 15:38 ` Jason Gunthorpe
2024-01-26 15:39 ` Timothy Pearson
2024-01-26 15:44 ` Timothy Pearson
2024-01-26 15:44 ` Jason Gunthorpe [this message]
2024-01-25 12:08 ` [PATCH 2/2] iommu: Fix the domain type checks when default_domain is set Shivaprasad G Bhat
2024-01-25 15:52 ` Jason Gunthorpe
2024-01-26 15:19 ` Shivaprasad G Bhat
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=20240126154427.GB50608@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=bgray@linux.ibm.com \
--cc=gbatra@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux.dev \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=sbhat@linux.ibm.com \
--cc=tpearson@raptorengineering.com \
--cc=vaibhav@linux.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).