From: Jason Gunthorpe <jgg@nvidia.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Baolu Lu <baolu.lu@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: Question about reserved_regions w/ Intel IOMMU
Date: Tue, 20 Jun 2023 13:55:47 -0300 [thread overview]
Message-ID: <ZJHaE2+XOgQj1q2k@nvidia.com> (raw)
In-Reply-To: <CAKgT0UccM=_D-gJdzjqeUmRZWnSHVaUABjgQBEamLYauE8WTCA@mail.gmail.com>
On Tue, Jun 20, 2023 at 07:57:57AM -0700, Alexander Duyck wrote:
> I think this may have gone off down a rathole as my original question
> wasn't anything about adding extra reserved regions. It was about
> exposing what the IOVA is already reserving so it could be user
> visible.
Your question points out that dma-iommu.c uses a different set of
reserved regions than everything else, and its set is closer to
functionally correct.
IMHO the resolution to what you are talking about is not to add more
debugging to dma-iommu but to make the set of reserved regions
consistently correct for everyone, which will make them viewable in
sysfs.
Jason
next prev parent reply other threads:[~2023-06-20 16:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 22:40 Question about reserved_regions w/ Intel IOMMU Alexander Duyck
2023-06-07 23:03 ` Alexander Duyck
2023-06-08 3:03 ` Baolu Lu
2023-06-08 14:33 ` Alexander Duyck
2023-06-08 15:38 ` Ashok Raj
2023-06-08 17:10 ` Alexander Duyck
2023-06-08 17:52 ` Ashok Raj
2023-06-08 18:15 ` Alexander Duyck
2023-06-08 18:02 ` Robin Murphy
2023-06-08 18:17 ` Alexander Duyck
2023-06-08 15:28 ` Robin Murphy
2023-06-13 15:54 ` Jason Gunthorpe
2023-06-16 8:39 ` Tian, Kevin
2023-06-16 12:20 ` Jason Gunthorpe
2023-06-16 15:27 ` Alexander Duyck
2023-06-16 16:34 ` Robin Murphy
2023-06-16 18:59 ` Jason Gunthorpe
2023-06-19 10:20 ` Robin Murphy
2023-06-19 14:02 ` Jason Gunthorpe
2023-06-20 14:57 ` Alexander Duyck
2023-06-20 16:55 ` Jason Gunthorpe [this message]
2023-06-20 17:47 ` Alexander Duyck
2023-06-21 11:30 ` Robin Murphy
2023-06-16 18:48 ` Jason Gunthorpe
2023-06-21 8:16 ` Tian, Kevin
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=ZJHaE2+XOgQj1q2k@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robin.murphy@arm.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).