From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Joerg Roedel <joerg.roedel@amd.com>, lkp <lkp@intel.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Samiullah Khawaja <skhawaja@google.com>
Subject: Re: [PATCH 3/3] iommupt: Avoid rewalking during map
Date: Mon, 19 Jan 2026 19:30:59 -0400 [thread overview]
Message-ID: <20260119233059.GV1134360@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB5276F66B367DA84472817F8B8C8CA@BN9PR11MB5276.namprd11.prod.outlook.com>
On Thu, Jan 15, 2026 at 06:44:06AM +0000, Tian, Kevin wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Monday, January 12, 2026 10:49 PM
> >
> > +int iommu_map_nosync(struct iommu_domain *domain, unsigned long
> > iova,
> > + phys_addr_t paddr, size_t size, int prot, gfp_t gfp)
> > +{
> > + struct pt_iommu *pt = iommupt_from_domain(domain);
> > +
> > + if (pt) {
> > + size_t mapped = 0;
> > + int ret;
> > +
> > + ret = pt->ops->map_range(pt, iova, paddr, size, prot, gfp,
> > + &mapped);
> > + if (ret) {
> > + iommu_unmap(domain, iova, mapped);
> > + return ret;
> > + }
>
> lack of trace_map() here if succeeds
Ah unmap has the same miss too thanks
Jason
next prev parent reply other threads:[~2026-01-19 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 14:49 [PATCH 0/3] Let iommupt manage changes in page size internally Jason Gunthorpe
2026-01-12 14:49 ` [PATCH 1/3] iommupt: Make pt_feature() always_inline Jason Gunthorpe
2026-01-14 8:15 ` Tian, Kevin
2026-01-12 14:49 ` [PATCH 2/3] iommupt: Directly call iommupt's unmap_range() Jason Gunthorpe
2026-01-15 6:17 ` Tian, Kevin
2026-01-15 18:26 ` Samiullah Khawaja
2026-01-12 14:49 ` [PATCH 3/3] iommupt: Avoid rewalking during map Jason Gunthorpe
2026-01-15 4:12 ` Samiullah Khawaja
2026-01-19 23:40 ` Jason Gunthorpe
2026-01-15 6:44 ` Tian, Kevin
2026-01-19 23:30 ` Jason Gunthorpe [this message]
2026-01-18 9:47 ` [PATCH 0/3] Let iommupt manage changes in page size internally Joerg Roedel
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=20260119233059.GV1134360@nvidia.com \
--to=jgg@nvidia.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=iommu@lists.linux.dev \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=lkp@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.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