From patchwork Sun Apr 21 01:44:27 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Pasha Tatashin X-Patchwork-Id: 10910435 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 6634F13B5 for ; Sun, 21 Apr 2019 01:44:36 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 481EE28965 for ; Sun, 21 Apr 2019 01:44:36 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 32AD428974; Sun, 21 Apr 2019 01:44:36 +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.7 required=2.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 177E428950 for ; Sun, 21 Apr 2019 01:44:34 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id 74C1F211FB88D; Sat, 20 Apr 2019 18:44:34 -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=2607:f8b0:4864:20::843; helo=mail-qt1-x843.google.com; envelope-from=pasha.tatashin@soleen.com; receiver=linux-nvdimm@lists.01.org Received: from mail-qt1-x843.google.com (mail-qt1-x843.google.com [IPv6:2607:f8b0:4864:20::843]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0CEE7211F9D74 for ; Sat, 20 Apr 2019 18:44:33 -0700 (PDT) Received: by mail-qt1-x843.google.com with SMTP id f13so8598815qto.6 for ; Sat, 20 Apr 2019 18:44:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=soleen.com; s=google; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=EUzJcCEPNzxrNRebVTHnadob9f3kjrf4lY7mTXNycVs=; b=bOYUDjSwgmBCuOhOjvyCWmoDmaFqDR+hSTrbz3hZ5hEnHqcNcOESI6IDbjkMh53cxB G2x/gsrquZNFLSsxAj32qOqLpwi+fd3+7zvGuUT/KEdN8aYwoHOWBkQGVACwskgHLMqt 3RPy+WduBUFt9ayw0hAttali1QHy8GoqBFz6WeuUUXLS0Cu7c1TkBjkjM6le/CDgWmDe xZWWQ851RPT7HzOEll57WaTFXsioXRv0XRhdEK5/qfxedQm63uqu26QBJLWmkYWWQ/Qm G+bddWTl2F+QpFsIAaDPs/kg0hNvLPx0miCR3utDHzsXmF+aBLXnELNjg0Jn811ftFkW c3RQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=EUzJcCEPNzxrNRebVTHnadob9f3kjrf4lY7mTXNycVs=; b=nlFZzRN2+POCDCHdozmlTHJv27FerUM4ORAbliGxkIJkdLnyhUHZNdepzYXHOGBGZq JcdPOPnF/9Z48pzLRa5dTnrY5psUcrE9vWeGHO6qaM94smC7pK0ctoRW1tFkRcpl1H24 RDq6PrT2mC1MftuQm1yw749BW47YeIGKCohd1jViEFKcGmCG54u9BaAYvODs848E5aGY Kj+t0tqDN4y3nK0E4LIYlwOmDnaa+HrU0kYAAwO6VnN9F8wcTsQXREkoHmxJP+45uBIx 9CiNmSHWq4QBCaxQGbnBrjWlRps9NOQtnrrtza/DwuCHLt3h5Uv/JjM/fA3GMDcD/xER P2fA== X-Gm-Message-State: APjAAAU/RVjwUuEZxZOq8dzIPNMHFHfZjas7qNhFt6ELtRoa9DukSd0e 8Exo5+gO9t/h0UAl3RR8I7Olyg== X-Google-Smtp-Source: APXvYqwGryHsI9e6T0GUZeIzujdwEDcVrbulda/4xor60EE28+izuI26XjYyBBq3siOOME8A8xbffQ== X-Received: by 2002:a0c:b7a5:: with SMTP id l37mr9708401qve.94.1555811072426; Sat, 20 Apr 2019 18:44:32 -0700 (PDT) Received: from localhost.localdomain (c-73-69-118-222.hsd1.nh.comcast.net. [73.69.118.222]) by smtp.gmail.com with ESMTPSA id u1sm1385218qtj.50.2019.04.20.18.44.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 20 Apr 2019 18:44:31 -0700 (PDT) From: Pavel Tatashin To: pasha.tatashin@soleen.com, jmorris@namei.org, sashal@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@lists.01.org, akpm@linux-foundation.org, mhocko@suse.com, dave.hansen@linux.intel.com, dan.j.williams@intel.com, keith.busch@intel.com, vishal.l.verma@intel.com, dave.jiang@intel.com, zwisler@kernel.org, thomas.lendacky@amd.com, ying.huang@intel.com, fengguang.wu@intel.com, bp@suse.de, bhelgaas@google.com, baiyaowei@cmss.chinamobile.com, tiwai@suse.de, jglisse@redhat.com Subject: [v2 0/2] "Hotremove" persistent memory Date: Sat, 20 Apr 2019 21:44:27 -0400 Message-Id: <20190421014429.31206-1-pasha.tatashin@soleen.com> X-Mailer: git-send-email 2.21.0 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: , Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" X-Virus-Scanned: ClamAV using ClamSMTP Changelog: v2 - Dan Williams mentioned that drv->remove() return is ignored by unbind. Unbind always succeeds. Because we cannot guarantee that memory can be offlined from the driver, don't even attempt to do so. Simply check that every section is offlined beforehand and only then proceed with removing dax memory. --- Recently, adding a persistent memory to be used like a regular RAM was added to Linux. This work extends this functionality to also allow hot removing persistent memory. We (Microsoft) have an important use case for this functionality. The requirement is for physical machines with small amount of RAM (~8G) to be able to reboot in a very short period of time (<1s). Yet, there is a userland state that is expensive to recreate (~2G). The solution is to boot machines with 2G preserved for persistent memory. Copy the state, and hotadd the persistent memory so machine still has all 8G available for runtime. Before reboot, offline and hotremove device-dax 2G, copy the memory that is needed to be preserved to pmem0 device, and reboot. The series of operations look like this: 1. After boot restore /dev/pmem0 to ramdisk to be consumed by apps. and free ramdisk. 2. Convert raw pmem0 to devdax ndctl create-namespace --mode devdax --map mem -e namespace0.0 -f 3. Hotadd to System RAM echo dax0.0 > /sys/bus/dax/drivers/device_dax/unbind echo dax0.0 > /sys/bus/dax/drivers/kmem/new_id echo online_movable > /sys/devices/system/memoryXXX/state 4. Before reboot hotremove device-dax memory from System RAM echo offline > /sys/devices/system/memoryXXX/state echo dax0.0 > /sys/bus/dax/drivers/kmem/unbind 5. Create raw pmem0 device ndctl create-namespace --mode raw -e namespace0.0 -f 6. Copy the state that was stored by apps to ramdisk to pmem device 7. Do kexec reboot or reboot through firmware if firmware does not zero memory in pmem0 region (These machines have only regular volatile memory). So to have pmem0 device either memmap kernel parameter is used, or devices nodes in dtb are specified. Pavel Tatashin (2): device-dax: fix memory and resource leak if hotplug fails device-dax: "Hotremove" persistent memory that is used like normal RAM drivers/dax/dax-private.h | 2 + drivers/dax/kmem.c | 96 +++++++++++++++++++++++++++++++++++++-- 2 files changed, 93 insertions(+), 5 deletions(-)