From: Jason Gunthorpe <jgg@nvidia.com>
To: 季杰 <jijie.ji@linux.alibaba.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Baolu Lu <baolu.lu@linux.intel.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xianting.tian@linux.alibaba.com"
<xianting.tian@linux.alibaba.com>,
"kaijieguo@linux.alibaba.com" <kaijieguo@linux.alibaba.com>,
"daishengdong@yeah.net" <daishengdong@yeah.net>,
"Zhao, Yan Y" <yan.y.zhao@intel.com>
Subject: Re: [PATCH] iommu/vt-d: Atomic breakdown of IOPT into finer granularity
Date: Tue, 15 Aug 2023 08:31:07 -0300 [thread overview]
Message-ID: <ZNth+6SE3lHu+uce@nvidia.com> (raw)
In-Reply-To: <ae72631d-31a4-eba0-b2f3-de4cf6c7d067@linux.alibaba.com>
On Tue, Aug 15, 2023 at 02:41:24PM +0800, 季杰 wrote:
> We do not incorporate iommufd in our cloud infrastructure, and use classic
> vfio and iommu driver. Cloud vendor like Aliyun may use its own IOPF handler
> software, so we want this patch to be a generic fix in iommu layer, suitable
> for both iommufd and vendor-specific software.
There will not be support for any advanced features in legacy
vfio. All new things will be in iommufd only.
Jason
next prev parent reply other threads:[~2023-08-15 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 12:10 [PATCH] iommu/vt-d: Atomic breakdown of IOPT into finer granularity Jie Ji
2023-08-14 12:15 ` Xianting Tian
2023-08-15 2:05 ` Baolu Lu
2023-08-15 3:15 ` Tian, Kevin
[not found] ` <BN9PR11MB527619D76C1ACFA5B85E2DEB8C14A@BN9PR11MB5276.namprd11.prod.outlook.com>
2023-08-15 4:00 ` Tian, Kevin
[not found] ` <ae72631d-31a4-eba0-b2f3-de4cf6c7d067@linux.alibaba.com>
2023-08-15 11:31 ` Jason Gunthorpe [this message]
2023-08-15 14:34 ` Jason Gunthorpe
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=ZNth+6SE3lHu+uce@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@linux.intel.com \
--cc=daishengdong@yeah.net \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jijie.ji@linux.alibaba.com \
--cc=joro@8bytes.org \
--cc=kaijieguo@linux.alibaba.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=xianting.tian@linux.alibaba.com \
--cc=yan.y.zhao@intel.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