[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190717074124.GA21617@amd>
Date: Wed, 17 Jul 2019 09:41:24 +0200
From: Pavel Machek <pavel@....cz>
To: jglisse@...hat.com, ebaskakov@...dia.com, jhubbard@...dia.com,
mhairgrove@...dia.com, SCheung@...dia.com, sgutti@...dia.com,
aneesh.kumar@...ux.vnet.ibm.com, bsingharora@...il.com,
benh@...nel.crashing.org, dan.j.williams@...el.com,
dnellans@...dia.com, hannes@...xchg.org,
kirill.shutemov@...ux.intel.com, mhocko@...nel.org,
paulmck@...ux.vnet.ibm.com, ross.zwisler@...ux.intel.com,
vdavydov.dev@...il.com, liubo95@...wei.com,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
kernel list <linux-kernel@...r.kernel.org>
Subject: HMM_MIRROR has less than useful help text
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
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists