From: Jason Gunthorpe <jgg@nvidia.com>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: <linux-rdma@vger.kernel.org>, <linux-mm@kvack.org>,
<nouveau@lists.freedesktop.org>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jerome Glisse <jglisse@redhat.com>,
John Hubbard <jhubbard@nvidia.com>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>, Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH v3 0/5] mm/hmm/nouveau: add PMD system memory mapping
Date: Fri, 10 Jul 2020 16:27:04 -0300 [thread overview]
Message-ID: <20200710192704.GA2128670@nvidia.com> (raw)
In-Reply-To: <20200701225352.9649-1-rcampbell@nvidia.com>
On Wed, Jul 01, 2020 at 03:53:47PM -0700, Ralph Campbell wrote:
> The goal for this series is to introduce the hmm_pfn_to_map_order()
> function. This allows a device driver to know that a given 4K PFN is
> actually mapped by the CPU using a larger sized CPU page table entry and
> therefore the device driver can safely map system memory using larger
> device MMU PTEs.
> The series is based on 5.8.0-rc3 and is intended for Jason Gunthorpe's
> hmm tree. These were originally part of a larger series:
> https://lore.kernel.org/linux-mm/20200619215649.32297-1-rcampbell@nvidia.com/
>
> Changes in v3:
> Replaced the HMM_PFN_P[MU]D flags with hmm_pfn_to_map_order() to
> indicate the size of the CPU mapping.
>
> Changes in v2:
> Make the hmm_range_fault() API changes into a separate series and add
> two output flags for PMD/PUD instead of a single compund page flag as
> suggested by Jason Gunthorpe.
> Make the nouveau page table changes a separate patch as suggested by
> Ben Skeggs.
> Only add support for 2MB nouveau mappings initially since changing the
> 1:1 CPU/GPU page table size assumptions requires a bigger set of changes.
> Rebase to 5.8.0-rc3.
>
> Ralph Campbell (5):
> nouveau/hmm: fault one page at a time
> mm/hmm: add hmm_mapping order
> nouveau: fix mapping 2MB sysmem pages
> nouveau/hmm: support mapping large sysmem pages
> hmm: add tests for HMM_PFN_PMD flag
Applied to hmm.git.
I edited the comment for hmm_pfn_to_map_order() and added a function
to compute the field.
Thanks,
Jason
next prev parent reply other threads:[~2020-07-10 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 22:53 Ralph Campbell
2020-07-01 22:53 ` [PATCH v3 1/5] nouveau/hmm: fault one page at a time Ralph Campbell
2020-07-01 22:53 ` [PATCH v3 2/5] mm/hmm: add hmm_mapping order Ralph Campbell
2020-07-01 22:53 ` [PATCH v3 3/5] nouveau: fix mapping 2MB sysmem pages Ralph Campbell
2020-07-08 3:19 ` [Nouveau] " Ben Skeggs
2020-07-01 22:53 ` [PATCH v3 4/5] nouveau/hmm: support mapping large " Ralph Campbell
2020-07-01 22:53 ` [PATCH v3 5/5] hmm: add tests for hmm_pfn_to_map_order() Ralph Campbell
2020-07-10 19:27 ` Jason Gunthorpe [this message]
2020-07-10 20:13 ` [PATCH v3 0/5] mm/hmm/nouveau: add PMD system memory mapping Ralph Campbell
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=20200710192704.GA2128670@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=bskeggs@redhat.com \
--cc=hch@lst.de \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rcampbell@nvidia.com \
--cc=shuah@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