All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: jglisse@redhat.com, ebaskakov@nvidia.com, jhubbard@nvidia.com,
	mhairgrove@nvidia.com, SCheung@nvidia.com, sgutti@nvidia.com,
	aneesh.kumar@linux.vnet.ibm.com, bsingharora@gmail.com,
	benh@kernel.crashing.org, dan.j.williams@intel.com,
	dnellans@nvidia.com, hannes@cmpxchg.org,
	kirill.shutemov@linux.intel.com, mhocko@kernel.org,
	paulmck@linux.vnet.ibm.com, ross.zwisler@linux.intel.com,
	vdavydov.dev@gmail.com, liubo95@huawei.com,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	kernel list <linux-kernel@vger.kernel.org>
Subject: HMM_MIRROR has less than useful help text
Date: Wed, 17 Jul 2019 09:41:24 +0200	[thread overview]
Message-ID: <20190717074124.GA21617@amd> (raw)

[-- Attachment #1: Type: text/plain, Size: 969 bytes --]

Hi!

Commit c0b124054f9e42eb6da545a10fe9122a7d7c3f72 has very nice commit
message, explaining what HMM_MIRROR is and when it is
needed. Unfortunately, it did not make it into Kconfig help:

CONFIG_HMM_MIRROR:

Select HMM_MIRROR if you want to mirror range of the CPU page table of
a
process into a device page table. Here, mirror means "keep
synchronized".
Prerequisites: the device must provide the ability to write-protect
its
page tables (at PAGE_SIZE granularity), and must be able to recover
from
the resulting potential page faults.

Could that be fixed?

This is key information for me:

# This is a heterogeneous memory management (HMM) process address space
# mirroring.
# This is useful for NVidia GPU >= Pascal, Mellanox IB >= mlx5 and more
# hardware in the future.

Thanks,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2019-07-17  7:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  7:41 Pavel Machek [this message]
2019-07-18 11:03 ` HMM_MIRROR has less than useful help text Balbir Singh
2019-07-18 14:25   ` Dan Williams
2019-07-18 16:36     ` Pavel Machek
2019-07-19  1:32 ` [PATCH] mm/Kconfig: additional help text for HMM_MIRROR option john.hubbard
2019-07-19  4:34   ` Ira Weiny
2019-07-19  5:15     ` John Hubbard
2019-07-19  5:57   ` Christoph Hellwig
2019-07-19 10:52     ` Pavel Machek
2019-07-19 11:48       ` Jason Gunthorpe
2019-07-19 12:00         ` Christoph Hellwig
2019-07-19 12:04           ` Pavel Machek
2019-07-19 20:38             ` John Hubbard
2019-07-22 11:58               ` Jason Gunthorpe
2019-07-22 12:01                 ` Christoph Hellwig

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=20190717074124.GA21617@amd \
    --to=pavel@ucw.cz \
    --cc=SCheung@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bsingharora@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=dnellans@nvidia.com \
    --cc=ebaskakov@nvidia.com \
    --cc=hannes@cmpxchg.org \
    --cc=jglisse@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo95@huawei.com \
    --cc=mhairgrove@nvidia.com \
    --cc=mhocko@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=sgutti@nvidia.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vdavydov.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.