Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1795236imm; Thu, 9 Aug 2018 02:00:55 -0700 (PDT) X-Google-Smtp-Source: AA+uWPxsrS8rTfLNvMvxIFIit34uD5oovcWLsmlIiHsMYHbSIrDqie5MStibNS5CtBn0Vi97pv44 X-Received: by 2002:a63:1902:: with SMTP id z2-v6mr1306083pgl.86.1533805255021; Thu, 09 Aug 2018 02:00:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533805254; cv=none; d=google.com; s=arc-20160816; b=LGgs1wvw1wljtAUGTStYyQ6ixfr1ZEIr1gzB9StgrOv86OiYcZKD9Bj+uKSYa/FYc4 DX6kQKd17LRzM55SwRzvLP+TjWJsKqMqECdS2YWVx+jcCUbwGmgyL/MLcOCd1fcXXB+3 tq4yCUgobjDwPwgxSqWkOgbuL/U8R+Wj2+covvQ1pwOfvwrXtsyv3BM//uhnAvxrdliW rvMcBilvgTp129lPDxpZ0X4FuotoUFJBXjPMqfubXYlf96KEwmUBrRZ5lzzx4HbP1Z0U esofR8VrOigLgPoMabjsLpl00Z+/Z90YfhLfsuL8y+c/1fFYQezzaMAwz4NCURKpcpGx tfdg== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=h2NltghaL7OJB2LziwmSP8RQoBZMzDQOgB2h7f4B6XY=; b=l9VRNq4nn1pIRElTCCv/I9TLuRgtAxjpf6gqlum14Rcn2PUKmLf13prigc7fpS2Hik 5dk9569q8+nwstYz509Ukvn1cFyg58PQckTWx5hGIkrT4miMbxgUemuIocOgMtxp0ytY 7QoZxEU/41TZ/N60QMhKBAMNgKxvnDhcJJ95DllWLn9x5jPq6wFpmr90wL22LiA+vSO5 GvfxHhir5zwC5J14EMe9KADKBvgITmADFoNVMVxx+F5I4mRSo/WorLBtS6VPBPwaoqAh XeOEs4qK/ONj+JrZxDEg/4Bx9nHkiLhJYIQiKdIlBbhrjEsIDGC8+OiKKNQvipOiz3qV fhDQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s10-v6si6496292pgm.501.2018.08.09.02.00.40; Thu, 09 Aug 2018 02:00:54 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729957AbeHILXe (ORCPT + 99 others); Thu, 9 Aug 2018 07:23:34 -0400 Received: from mx2.suse.de ([195.135.220.15]:36298 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729393AbeHILXd (ORCPT ); Thu, 9 Aug 2018 07:23:33 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id D7963ACE4; Thu, 9 Aug 2018 08:59:40 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 7238E1E3C98; Thu, 9 Aug 2018 10:59:40 +0200 (CEST) Date: Thu, 9 Aug 2018 10:59:40 +0200 From: Jan Kara To: Zhang Yi Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org, pbonzini@redhat.com, dan.j.williams@intel.com, jack@suse.cz, hch@lst.de, yu.c.zhang@intel.com, linux-mm@kvack.org, rkrcmar@redhat.com, yi.z.zhang@intel.com Subject: Re: [PATCH V3 2/4] mm: introduce memory type MEMORY_DEVICE_DEV_DAX Message-ID: <20180809085940.GC5069@quack2.suse.cz> References: <01aaca83694c3b0093fcb2f48af1dff0b147a4b2.1533811181.git.yi.z.zhang@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01aaca83694c3b0093fcb2f48af1dff0b147a4b2.1533811181.git.yi.z.zhang@linux.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 09-08-18 18:53:08, Zhang Yi wrote: > Currently, NVDIMM pages will be marked 'PageReserved'. However, unlike > other reserved PFNs, pages on NVDIMM shall still behave like normal ones > in many cases, i.e. when used as backend memory of KVM guest. This patch > introduces a new memory type, MEMORY_DEVICE_DEV_DAX. And set this flag > while dax driver hotplug the device memory. > > Signed-off-by: Zhang Yi > Signed-off-by: Zhang Yu Looks good to me now. You can add: Reviewed-by: Jan Kara Honza > --- > drivers/dax/pmem.c | 1 + > include/linux/memremap.h | 8 ++++++++ > 2 files changed, 9 insertions(+) > > diff --git a/drivers/dax/pmem.c b/drivers/dax/pmem.c > index fd49b24..fb3f363 100644 > --- a/drivers/dax/pmem.c > +++ b/drivers/dax/pmem.c > @@ -111,6 +111,7 @@ static int dax_pmem_probe(struct device *dev) > return rc; > > dax_pmem->pgmap.ref = &dax_pmem->ref; > + dax_pmem->pgmap.type = MEMORY_DEVICE_DEV_DAX; > addr = devm_memremap_pages(dev, &dax_pmem->pgmap); > if (IS_ERR(addr)) > return PTR_ERR(addr); > diff --git a/include/linux/memremap.h b/include/linux/memremap.h > index f91f9e7..cd07ca8 100644 > --- a/include/linux/memremap.h > +++ b/include/linux/memremap.h > @@ -53,11 +53,19 @@ struct vmem_altmap { > * wakeup event whenever a page is unpinned and becomes idle. This > * wakeup is used to coordinate physical address space management (ex: > * fs truncate/hole punch) vs pinned pages (ex: device dma). > + * > + * MEMORY_DEVICE_DEV_DAX: > + * Device memory that support raw access to persistent memory. Without need > + * of an intervening filesystem, it could be directed mapped via an mmap > + * capable character device. Together with the type MEMORY_DEVICE_FS_DAX, > + * we could distinguish the persistent memory pages from normal ZONE_DEVICE > + * pages. > */ > enum memory_type { > MEMORY_DEVICE_PRIVATE = 1, > MEMORY_DEVICE_PUBLIC, > MEMORY_DEVICE_FS_DAX, > + MEMORY_DEVICE_DEV_DAX, > }; > > /* > -- > 2.7.4 > -- Jan Kara SUSE Labs, CR