From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752612AbdKLAPi (ORCPT <rfc822;w@1wt.eu>);
        Sat, 11 Nov 2017 19:15:38 -0500
Received: from imap.thunk.org ([74.207.234.97]:36228 "EHLO imap.thunk.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752123AbdKLAPg (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 11 Nov 2017 19:15:36 -0500
Date: Sat, 11 Nov 2017 19:15:31 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: [pmem_attach_disk] WARNING: CPU: 46 PID: 518 at
 kernel/memremap.c:363 devm_memremap_pages+0x350/0x4b0
Message-ID: <20171112001531.m23yeuuiqmawlbhj@thunk.org>
Mail-Followup-To: Theodore Ts'o <tytso@mit.edu>,
        Dan Williams <dan.j.williams@intel.com>,
        Fengguang Wu <fengguang.wu@intel.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Vishal Verma <vishal.l.verma@intel.com>
References: <CA+55aFxSJGeN=2X-uX-on1Uq2Nb8+v1aiMDz5H1+tKW_N5Q+6g@mail.gmail.com>
 <20171029225155.qcum5i75awrt5tzm@wfg-t540p.sh.intel.com>
 <20171030074055.wd56v3wiy2aveh2p@wfg-t540p.sh.intel.com>
 <CAPcyv4gPQsTFAuOX_zcuQcxZsesBDX24cm3k6WPK0YifuwBTzw@mail.gmail.com>
 <20171031000053.gdn5jbxhlrxqmxfq@wfg-t540p.sh.intel.com>
 <CAPcyv4hVzbOF2VxGycsCSdH6Gb42P4=LJGaYkrdK+CfKcjUspQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPcyv4hVzbOF2VxGycsCSdH6Gb42P4=LJGaYkrdK+CfKcjUspQ@mail.gmail.com>
User-Agent: NeoMutt/20170609 (1.8.3)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Oct 30, 2017 at 05:24:42PM -0700, Dan Williams wrote:
> 
> Something is going wrong with memmap= because you are not getting 1G
> aligned address ranges. I think you would have better luck switching
> to the official nvdimm emulation in qemu-kvm rather than relying on
> memmap= which is just a fragile / unreliable interface. In fact we
> should look to deprecate it and point everyone to use the standard
> methods. We just have a problem of legacy pre-ACPI6 platforms that
> have no other way than a kernel command line to identify persistent
> memory ranges.

Why is memmap fragile/unreliable?  I'm not using qemu-kvm for most of
my testing and right now memmap is the only way I can test ext4 DAX
codepaths.   :-/

						- Ted