From patchwork Wed Oct 31 03:12:49 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dan Williams X-Patchwork-Id: 10662021 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id E2F1813B5 for ; Wed, 31 Oct 2018 03:24:39 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C4D2B2A440 for ; Wed, 31 Oct 2018 03:24:39 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B56642A594; Wed, 31 Oct 2018 03:24:39 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 474032A440 for ; Wed, 31 Oct 2018 03:24:39 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id D2A3621184E68; Tue, 30 Oct 2018 20:24:38 -0700 (PDT) X-Original-To: linux-nvdimm@lists.01.org Delivered-To: linux-nvdimm@lists.01.org Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.24; helo=mga09.intel.com; envelope-from=dan.j.williams@intel.com; receiver=linux-nvdimm@lists.01.org Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 72D4C2116DF85 for ; Tue, 30 Oct 2018 20:24:38 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Oct 2018 20:24:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,447,1534834800"; d="scan'208";a="92552362" Received: from dwillia2-desk3.jf.intel.com (HELO dwillia2-desk3.amr.corp.intel.com) ([10.54.39.16]) by FMSMGA003.fm.intel.com with ESMTP; 30 Oct 2018 20:24:37 -0700 Subject: [PATCH 0/8] Introduce a device-dax bus-based device-model From: Dan Williams To: linux-nvdimm@lists.01.org Date: Tue, 30 Oct 2018 20:12:49 -0700 Message-ID: <154095556915.3271337.12581429676272726902.stgit@dwillia2-desk3.amr.corp.intel.com> User-Agent: StGit/0.18-2-gc94f MIME-Version: 1.0 X-BeenThere: linux-nvdimm@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Linux-nvdimm developer list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-mm@kvack.org, dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" X-Virus-Scanned: ClamAV using ClamSMTP Prompted by the review of "[PATCH 0/9] Allow persistent memory to be used like normal RAM" [1] introduce a new bus / device-driver-model for device-dax. Currently device-dax instances result from attaching an nvdimm namespace device to the dax_pmem driver. These instances are registered with the /sys/class/dax sub-system. With the expectation that platforms will describe performance differentiated memory [2] for ranges other than persistent memory (pmem) a new device-model is needed. Arrange for dax_pmem to be one of potentially several drivers that know how to discover differentiated memory and register a device instance on the dax bus. The expectation is that, by default, this device is consumed by the typical device-dax driver that will expose the range through a /dev/daxX.Y character device. Optionally other drivers can consume the dax device instance. For example, the kmem driver [1] can attach to device-dax device instance to hot-add the related memory range to the core page-allocator. Going forward, provider drivers outside of dax_pmem can be created to register other memories with unique performance properties. Since /sys/class/dax is a released ABI, a compat driver is provided so that distros can opt-in to the new bus based ABI. The /sys/class/dax interface is then deprecated and scheduled to be removed. [1]: https://lkml.org/lkml/2018/10/23/9 [2]: Section 5.2.27 Heterogeneous Memory Attribute Table (HMAT) http://www.uefi.org/sites/default/files/resources/ACPI%206_2_A_Sept29.pdf --- Dan Williams (8): device-dax: Kill dax_region ida device-dax: Kill dax_region base device-dax: Remove multi-resource infrastructure device-dax: Start defining a dax bus model device-dax: Introduce bus + driver model device-dax: Move resource pinning+mapping into the common driver device-dax: Add support for a dax override driver device-dax: Add /sys/class/dax backwards compatibility Documentation/ABI/obsolete/sysfs-class-dax | 22 + drivers/dax/Kconfig | 12 + drivers/dax/Makefile | 5 drivers/dax/bus.c | 449 ++++++++++++++++++++++++++++ drivers/dax/bus.h | 60 ++++ drivers/dax/dax-private.h | 30 +- drivers/dax/dax.h | 18 - drivers/dax/device-dax.h | 25 -- drivers/dax/device.c | 365 +++++------------------ drivers/dax/pmem.c | 161 ---------- drivers/dax/pmem/Makefile | 7 drivers/dax/pmem/compat.c | 73 +++++ drivers/dax/pmem/core.c | 69 ++++ drivers/dax/pmem/pmem.c | 40 ++ drivers/dax/super.c | 41 ++- tools/testing/nvdimm/Kbuild | 7 tools/testing/nvdimm/dax-dev.c | 16 - 17 files changed, 880 insertions(+), 520 deletions(-) create mode 100644 Documentation/ABI/obsolete/sysfs-class-dax create mode 100644 drivers/dax/bus.c create mode 100644 drivers/dax/bus.h delete mode 100644 drivers/dax/dax.h delete mode 100644 drivers/dax/device-dax.h delete mode 100644 drivers/dax/pmem.c create mode 100644 drivers/dax/pmem/Makefile create mode 100644 drivers/dax/pmem/compat.c create mode 100644 drivers/dax/pmem/core.c create mode 100644 drivers/dax/pmem/pmem.c