From: Lorenzo Stoakes <lstoakes@gmail.com>
To: Alistair Popple <apopple@nvidia.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
Vinod Koul <vkoul@kernel.org>,
"Jiang, Dave" <dave.jiang@intel.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"Zhu, Tony" <tony.zhu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Christoph Hellwig <hch@infradead.org>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>
Subject: Re: [PATCH 09/17] mm: export access_remote_vm() symbol
Date: Thu, 5 Jan 2023 07:26:10 +0000 [thread overview]
Message-ID: <Y7Z7kjnaEk1qwRi8@lucifer> (raw)
In-Reply-To: <87k021vnmw.fsf@nvidia.com>
On Thu, Jan 05, 2023 at 10:57:02AM +1100, Alistair Popple wrote:
> Ok, although I think making this an iommu specific wrapper taking a
> PASID rather than mm_struct would make the API more specific and less
> likely to be misused as the mm_count/users lifetime issues could be
> dealt with inside the core IOMMU code.
This sounds like the ideal approach, as long as we either mmgrab() or otherwise
ensure that the mm won't disappear underneath us, then use mmget_not_zero() to
get a reference in this wrapper function, I think we're gravy.
next prev parent reply other threads:[~2023-01-05 7:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 16:34 [PATCH 00/17] Enable DSA 2.0 Event Log and completion record faulting features Fenghua Yu
2023-01-03 16:34 ` [PATCH 01/17] dmaengine: idxd: make misc interrupt one shot Fenghua Yu
2023-01-03 16:34 ` [PATCH 02/17] dmaengine: idxd: add event log size sysfs attribute Fenghua Yu
2023-01-03 16:34 ` [PATCH 03/17] dmaengine: idxd: setup event log configuration Fenghua Yu
2023-01-03 16:34 ` [PATCH 04/17] dmaengine: idxd: add interrupt handling for event log Fenghua Yu
2023-01-03 16:34 ` [PATCH 05/17] dmanegine: idxd: add debugfs for event log dump Fenghua Yu
2023-01-03 16:34 ` [PATCH 06/17] dmaengine: idxd: add per DSA wq workqueue for processing cr faults Fenghua Yu
2023-01-03 16:34 ` [PATCH 07/17] dmaengine: idxd: create kmem cache for event log fault items Fenghua Yu
2023-01-03 16:34 ` [PATCH 08/17] iommu: expose iommu_sva_find() to common header Fenghua Yu
2023-01-03 16:34 ` [PATCH 09/17] mm: export access_remote_vm() symbol Fenghua Yu
2023-01-03 17:45 ` Lorenzo Stoakes
2023-01-03 17:50 ` Lorenzo Stoakes
2023-01-03 19:20 ` Yu, Fenghua
2023-01-03 20:13 ` Lorenzo Stoakes
2023-01-04 5:06 ` Yu, Fenghua
2023-01-04 6:12 ` Alistair Popple
2023-01-04 19:00 ` Yu, Fenghua
2023-01-04 20:00 ` Lorenzo Stoakes
2023-01-04 19:56 ` Lorenzo Stoakes
2023-01-04 21:05 ` Lorenzo Stoakes
2023-01-04 23:57 ` Alistair Popple
2023-01-05 3:08 ` Yu, Fenghua
2023-01-05 3:22 ` Alistair Popple
2023-01-05 20:58 ` Yu, Fenghua
2023-01-05 21:04 ` Lorenzo Stoakes
2023-01-05 7:26 ` Lorenzo Stoakes [this message]
2023-01-08 17:36 ` Christoph Hellwig
2023-03-01 23:39 ` Fenghua Yu
2023-01-03 16:34 ` [PATCH 10/17] dmaengine: idxd: process user page faults for completion record Fenghua Yu
2023-01-03 16:34 ` [PATCH 11/17] dmaengine: idxd: add descs_completed field " Fenghua Yu
2023-01-03 16:35 ` [PATCH 12/17] dmaengine: idxd: process batch descriptor completion record faults Fenghua Yu
2023-01-03 16:35 ` [PATCH 13/17] dmaengine: idxd: add per file user counters for " Fenghua Yu
2023-01-03 16:35 ` [PATCH 14/17] dmaengine: idxd: add a device to represent the file opened Fenghua Yu
2023-01-03 16:35 ` [PATCH 15/17] dmaengine: idxd: expose fault counters to sysfs Fenghua Yu
2023-01-03 16:35 ` [PATCH 16/17] dmaengine: idxd: add pid to exported sysfs attribute for opened file Fenghua Yu
2023-01-03 16:35 ` [PATCH 17/17] dmaengine: idxd: add per wq PRS disable Fenghua Yu
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=Y7Z7kjnaEk1qwRi8@lucifer \
--to=lstoakes@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ravi.v.shankar@intel.com \
--cc=tony.zhu@intel.com \
--cc=vkoul@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