Received: by 2002:a25:5b86:0:0:0:0:0 with SMTP id p128csp1071996ybb; Thu, 28 Mar 2019 19:06:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqysWyY4+8FdNcFf7OICW1T+KBxqKfEZBLbm77saD+uA8qJRm5ZOPm/L7Np1naFW8tmj35v+ X-Received: by 2002:a63:3f8d:: with SMTP id m135mr4002056pga.228.1553825191117; Thu, 28 Mar 2019 19:06:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553825191; cv=none; d=google.com; s=arc-20160816; b=x31TZpjrlWFyKHWZHg0Mp+jpT3wpn1h7H3nWvLprt+gT6tRBxX6GQVQLxpuWbU3YnC 2dDECRsW+LJv6aF94qz0Y0ZYdkWL0QJgpr/cRq9U8chNKAB93kPV5b7wIRDFrtkIz44f 9pail+9BARY0Fez4T/5Dklv+WfaCPYIO8y9ukMtJnoVXPahNQ+MeKtFIGc/XV/+T10dH lfyLPlJpwoGjovbEHIYCm2xVymHB7SAm5l6a+XNHnqyJxyEQ6XLmjDha3wuYy72KfDC2 7seD8K42EZIBBv1Z/m6Sdpppp4chmWWiIgvafP9A1YPnxk7afJ3z9ngpMUq5UJZsdPmJ 0Jgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=npeFvWz1UKVM4wlSOd5g612PH6kgpRLjs4ih0B9n87s=; b=OHfzckb9kPV5qLkwkEXaxCXEJAu7jiLEj1M7ohat4RkoC8J31XxyWCtao1l/ByGlex 0Y5x9l9oSZJ3NCDzoG5AilIn6TDO12CcgRcyQPRLanZqmmOaF3nnCPQnkHfDwhD4YDyJ o7o8TpGSIfFMffHi6XncCDcBqYHg6cYHa9u+VMwNN0i9AucdzB12KxlCSh6TSp+CYvV0 ui2Cz+trhRsSorQpM0fadAUDKFxn0a0ekeisZ8iLjHMLFYWpvhHl1uFRpEJVHqzYXCge Gwg9azYMcSW+s6SqKN/S3wsDJ2nsyPjiXSd9mNAVwP3GA2CCKqvIAFGYhR8S33rivWhZ 8Y7Q== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o11si718579pgv.13.2019.03.28.19.06.15; Thu, 28 Mar 2019 19:06:31 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728637AbfC2CFe (ORCPT + 99 others); Thu, 28 Mar 2019 22:05:34 -0400 Received: from mga07.intel.com ([134.134.136.100]:55750 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727938AbfC2CFe (ORCPT ); Thu, 28 Mar 2019 22:05:34 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Mar 2019 19:05:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,282,1549958400"; d="scan'208";a="138333451" Received: from iweiny-desk2.sc.intel.com ([10.3.52.157]) by fmsmga007.fm.intel.com with ESMTP; 28 Mar 2019 19:05:32 -0700 Date: Thu, 28 Mar 2019 11:04:26 -0700 From: Ira Weiny To: jglisse@redhat.com Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Dan Williams , John Hubbard , Arnd Bergmann Subject: Re: [PATCH v2 09/11] mm/hmm: allow to mirror vma of a file on a DAX backed filesystem v2 Message-ID: <20190328180425.GI31324@iweiny-DESK2.sc.intel.com> References: <20190325144011.10560-1-jglisse@redhat.com> <20190325144011.10560-10-jglisse@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190325144011.10560-10-jglisse@redhat.com> User-Agent: Mutt/1.11.1 (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 25, 2019 at 10:40:09AM -0400, Jerome Glisse wrote: > From: J?r?me Glisse > > HMM mirror is a device driver helpers to mirror range of virtual address. > It means that the process jobs running on the device can access the same > virtual address as the CPU threads of that process. This patch adds support > for mirroring mapping of file that are on a DAX block device (ie range of > virtual address that is an mmap of a file in a filesystem on a DAX block > device). There is no reason to not support such case when mirroring virtual > address on a device. > > Note that unlike GUP code we do not take page reference hence when we > back-off we have nothing to undo. > > Changes since v1: > - improved commit message > - squashed: Arnd Bergmann: fix unused variable warning in hmm_vma_walk_pud > > Signed-off-by: J?r?me Glisse > Reviewed-by: Ralph Campbell > Cc: Andrew Morton > Cc: Dan Williams > Cc: John Hubbard > Cc: Arnd Bergmann > --- > mm/hmm.c | 132 ++++++++++++++++++++++++++++++++++++++++++++++--------- > 1 file changed, 111 insertions(+), 21 deletions(-) > > diff --git a/mm/hmm.c b/mm/hmm.c > index 64a33770813b..ce33151c6832 100644 > --- a/mm/hmm.c > +++ b/mm/hmm.c > @@ -325,6 +325,7 @@ EXPORT_SYMBOL(hmm_mirror_unregister); > > struct hmm_vma_walk { > struct hmm_range *range; > + struct dev_pagemap *pgmap; > unsigned long last; > bool fault; > bool block; > @@ -499,6 +500,15 @@ static inline uint64_t pmd_to_hmm_pfn_flags(struct hmm_range *range, pmd_t pmd) > range->flags[HMM_PFN_VALID]; > } > > +static inline uint64_t pud_to_hmm_pfn_flags(struct hmm_range *range, pud_t pud) > +{ > + if (!pud_present(pud)) > + return 0; > + return pud_write(pud) ? range->flags[HMM_PFN_VALID] | > + range->flags[HMM_PFN_WRITE] : > + range->flags[HMM_PFN_VALID]; > +} > + > static int hmm_vma_handle_pmd(struct mm_walk *walk, > unsigned long addr, > unsigned long end, > @@ -520,8 +530,19 @@ static int hmm_vma_handle_pmd(struct mm_walk *walk, > return hmm_vma_walk_hole_(addr, end, fault, write_fault, walk); > > pfn = pmd_pfn(pmd) + pte_index(addr); > - for (i = 0; addr < end; addr += PAGE_SIZE, i++, pfn++) > + for (i = 0; addr < end; addr += PAGE_SIZE, i++, pfn++) { > + if (pmd_devmap(pmd)) { > + hmm_vma_walk->pgmap = get_dev_pagemap(pfn, > + hmm_vma_walk->pgmap); > + if (unlikely(!hmm_vma_walk->pgmap)) > + return -EBUSY; > + } > pfns[i] = hmm_pfn_from_pfn(range, pfn) | cpu_flags; > + } > + if (hmm_vma_walk->pgmap) { > + put_dev_pagemap(hmm_vma_walk->pgmap); > + hmm_vma_walk->pgmap = NULL; > + } > hmm_vma_walk->last = end; > return 0; > } > @@ -608,10 +629,24 @@ static int hmm_vma_handle_pte(struct mm_walk *walk, unsigned long addr, > if (fault || write_fault) > goto fault; > > + if (pte_devmap(pte)) { > + hmm_vma_walk->pgmap = get_dev_pagemap(pte_pfn(pte), > + hmm_vma_walk->pgmap); > + if (unlikely(!hmm_vma_walk->pgmap)) > + return -EBUSY; > + } else if (IS_ENABLED(CONFIG_ARCH_HAS_PTE_SPECIAL) && pte_special(pte)) { > + *pfn = range->values[HMM_PFN_SPECIAL]; > + return -EFAULT; > + } > + > *pfn = hmm_pfn_from_pfn(range, pte_pfn(pte)) | cpu_flags; > return 0; > > fault: > + if (hmm_vma_walk->pgmap) { > + put_dev_pagemap(hmm_vma_walk->pgmap); > + hmm_vma_walk->pgmap = NULL; > + } > pte_unmap(ptep); > /* Fault any virtual address we were asked to fault */ > return hmm_vma_walk_hole_(addr, end, fault, write_fault, walk); > @@ -699,12 +734,83 @@ static int hmm_vma_walk_pmd(pmd_t *pmdp, > return r; > } > } > + if (hmm_vma_walk->pgmap) { > + put_dev_pagemap(hmm_vma_walk->pgmap); > + hmm_vma_walk->pgmap = NULL; > + } Why is this here and not in hmm_vma_handle_pte()? Unless I'm just getting tired this is the corresponding put when hmm_vma_handle_pte() returns 0 above at above. Ira