From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommufd: Enforce IOMMU_RESV_SW_MSI upon hwpt_paging allocation
Date: Thu, 1 Aug 2024 10:39:12 -0700 [thread overview]
Message-ID: <ZqvIQFsgUGjqqjmF@Asurada-Nvidia> (raw)
In-Reply-To: <20240801132848.GE2809814@nvidia.com>
On Thu, Aug 01, 2024 at 10:28:48AM -0300, Jason Gunthorpe wrote:
> On Wed, Jul 31, 2024 at 11:23:24AM -0700, Nicolin Chen wrote:
> > > If we really want to go this route I wonder whether a per-IOMMU
> > > get_resv_regions() API should first exist then there is a clear definition
> > > what types are per-IOMMU and what are not.
> >
> > Probably it'd be necessary.
>
> But domains can cross IOMMU's as well, it is not per-iommu you are
> after but hardwired per-IOMMU driver type.
>
> What was the issue with trying to fix this on the nesting attach side?
No, seems that we all agreed on enforcing IOVAs to the parent
HWPT, so we will Just go on the nesting attach side.
Thanks
Nicolin
next prev parent reply other threads:[~2024-08-01 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 23:51 [PATCH] iommufd: Enforce IOMMU_RESV_SW_MSI upon hwpt_paging allocation Nicolin Chen
2024-07-29 18:24 ` Jason Gunthorpe
2024-07-29 20:05 ` Nicolin Chen
2024-07-31 7:50 ` Tian, Kevin
2024-07-31 18:23 ` Nicolin Chen
2024-08-01 13:28 ` Jason Gunthorpe
2024-08-01 17:39 ` Nicolin Chen [this message]
2024-07-31 7:45 ` Tian, Kevin
2024-07-31 18:13 ` Nicolin Chen
2024-07-31 21:21 ` Nicolin Chen
2024-08-01 8:10 ` Tian, Kevin
2024-08-01 17:40 ` Nicolin Chen
2024-08-01 14:10 ` 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=ZqvIQFsgUGjqqjmF@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@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