Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp2979032ybi; Thu, 18 Jul 2019 18:33:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqwn5x1PS7LMakhQn7AV+6Jrk7+Bo4gcGOq+UYy86J/kACCM5/SwMbcp4pzeHtB/D4MPT6Nx X-Received: by 2002:a17:902:7281:: with SMTP id d1mr52796499pll.329.1563500015177; Thu, 18 Jul 2019 18:33:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563500015; cv=none; d=google.com; s=arc-20160816; b=sj3uHM5IpD+uihwBrqo3Qc1PZkkeH9zK+UMpBohHkw5y+FMAKnH8rgYbbbQkV5G6HU 15buzhUCAw2YMqV23GuBKzVQT8Z17UP+CC4/GbSGblmA6Pthh3EGNOHTOzlM2/GN64T4 feMX05wLmYHMDNMo9DINtB8sFxt2wB/dywekoail0u5F+RHB5DJUFHEwaCJR0EZiS7Tb y2MP1C4b9VixnvHacqL/kXIHFUp+MH12s2UA09aB1vhjmJjulpnHoaG/2lGCtTqeG/0t 7LE4aukyOb2NEh3gD0Wpw7pj9z+Zpnw6s6TYnEvQ4GozzftvJ0ASk9q95dFsV+/atXWy Wehw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=I+WrorOfGfVMn+EPTDunKndruhB1A70dpJYU7D8HhjI=; b=V/VhB3wOXWdpWwThezlxCLeNyKja1AQMmv1CIKS82MU1LS8cdsMqWgw+GtJNMVsLFv ZxtUIEFHyrDpsWOzpT20bH6KqmaPUDguSn5KtZj8koMyK0L6wArUctoLx0+D73cXYsIr brEQAzGEcNVhfg0X1lsDDQGLoDyMiaGfOPyiTcINtmsgXRGbgDHCuPEVH1qvCE+hpyN+ ZpsOUIh3QcFTALjMEx8OMFn0v3PRuxVMJsniNskFTKcFRIjWwFQAdwY+hiXc/qOXlkK8 lMk5mfbGU3l+XuQGnKDteVwnus8NGZud74m/5osuMpUrkihpvz4csL9bJMu8BJuf2B4n cBVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=in+MPhQQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f10si3238493pgg.348.2019.07.18.18.33.18; Thu, 18 Jul 2019 18:33:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=in+MPhQQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726222AbfGSBc6 (ORCPT + 99 others); Thu, 18 Jul 2019 21:32:58 -0400 Received: from mail-pl1-f196.google.com ([209.85.214.196]:36705 "EHLO mail-pl1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726015AbfGSBc5 (ORCPT ); Thu, 18 Jul 2019 21:32:57 -0400 Received: by mail-pl1-f196.google.com with SMTP id k8so14796834plt.3 for ; Thu, 18 Jul 2019 18:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=I+WrorOfGfVMn+EPTDunKndruhB1A70dpJYU7D8HhjI=; b=in+MPhQQJrz8zMcoMjNaSmIfGzYsuCUMH2V5W913MXsyCZvH0sEDOWy3Z2CI5RsAef 78E2KyUu7xzy37ZFlPIY0Enj/CpzapB9228mVLOxaouvtgjRXwKzbXqypJdVYbiESDcU FNXKc7ni3Cc32pQ3a90864Zu7DRFCmnb4i4Hf/21nmOJoP698l25BVZ6DlPjLzc82ta/ dHVabGJJOayDSxkBrpEkvUD9Raze4jorP/ei56WnO1Ae5MUPSkn/sOaSgHMCgQ1RPBgR 1a1nzzHlL5OgOBFRia96vDTh8KvZqHpmDE0fwgszQBv4dedZh/M60Vic9Jy3mgT2gayH ChVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=I+WrorOfGfVMn+EPTDunKndruhB1A70dpJYU7D8HhjI=; b=gjoi+CbWFu3+XV6haOWHNdFrdkxKF+BiARGbaLy6NIB/RsRaGmw0B6d3hpRSJMyavf 7Ky9EbbAnY73mKF+buIsX3BhHuf9hJqc712VvqDu/lkzs20qepcF+7vmf3jOtL/cXBn0 8a+dxcewTMAiVFLcvHEVPlKH5H6hcD36sCfSApKcwuWiPxUKL4y1CgIrOXpwgjTLfuLY T2FCuqAd3SgF5NvghoNuYzM4CibGpmi+Gyc0O+IWjSOiWbg9YpCDuhkr5zSrxPTvVU5C pj4eJgHrNkblGFPHUzEHZ94WVeQRGibpxIf43DkLi/MLuPWKgqZvbwNSiym2cUdItRSe f09g== X-Gm-Message-State: APjAAAXYasicA0ZBijqgeeQoeTfwuchB9pmNNeiPjpP7xpYbj/zX1/ja gbkyUTeGcPnv0ZnUX4Ax82U= X-Received: by 2002:a17:902:9307:: with SMTP id bc7mr51975599plb.183.1563499977244; Thu, 18 Jul 2019 18:32:57 -0700 (PDT) Received: from blueforge.nvidia.com (searspoint.nvidia.com. [216.228.112.21]) by smtp.gmail.com with ESMTPSA id v184sm28887711pfb.82.2019.07.18.18.32.55 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 18 Jul 2019 18:32:56 -0700 (PDT) From: john.hubbard@gmail.com X-Google-Original-From: jhubbard@nvidia.com To: pavel@ucw.cz Cc: SCheung@nvidia.com, akpm@linux-foundation.org, aneesh.kumar@linux.vnet.ibm.com, benh@kernel.crashing.org, bsingharora@gmail.com, dan.j.williams@intel.com, dnellans@nvidia.com, ebaskakov@nvidia.com, hannes@cmpxchg.org, jglisse@redhat.com, jhubbard@nvidia.com, kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org, liubo95@huawei.com, mhairgrove@nvidia.com, mhocko@kernel.org, paulmck@linux.vnet.ibm.com, ross.zwisler@linux.intel.com, sgutti@nvidia.com, torvalds@linux-foundation.org, vdavydov.dev@gmail.com, Jason Gunthorpe , Christoph Hellwig Subject: [PATCH] mm/Kconfig: additional help text for HMM_MIRROR option Date: Thu, 18 Jul 2019 18:32:53 -0700 Message-Id: <20190719013253.17642-1-jhubbard@nvidia.com> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20190717074124.GA21617@amd> References: <20190717074124.GA21617@amd> MIME-Version: 1.0 X-NVConfidentiality: public Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: John Hubbard The HMM_MIRROR option in Kconfig is a little underdocumented and mysterious, and leaves people wondering whether to enable it. Add text explaining just a little bit more about HMM, and also mention which hardware would benefit from having HMM_MIRROR enabled. Suggested-by: Pavel Machek Cc: Balbir Singh Cc: Dan Williams Cc: Jason Gunthorpe Cc: Jerome Glisse Cc: Christoph Hellwig Signed-off-by: John Hubbard --- Hi Pavel and all, does this help? I've tried to capture the key missing bits of documentation, but still keep it small, for Kconfig. thanks, John Hubbard NVIDIA mm/Kconfig | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/mm/Kconfig b/mm/Kconfig index 56cec636a1fc..2fcb92e7f696 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -681,11 +681,18 @@ config HMM_MIRROR depends on MMU && 64BIT select MMU_NOTIFIER help - 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. + This is Heterogeneous Memory Management (HMM) process address space + mirroring. + + HMM_MIRROR provides a way to mirror ranges of the CPU page tables + 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. + + Select HMM_MIRROR if you have hardware that meets the above + description. An early, partial list of such hardware is: + an NVIDIA GPU >= Pascal, Mellanox IB >= mlx5, or an AMD GPU. config DEVICE_PRIVATE bool "Unaddressable device memory (GPU memory, ...)" -- 2.22.0