Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3259194imu; Mon, 28 Jan 2019 01:27:57 -0800 (PST) X-Google-Smtp-Source: ALg8bN7Oi/u9XSMQKeq/fy/UBa66h/eFMZRl5JGlA7pOemcI2n82h8mOAnT4uiHucgyKhx0I6PMu X-Received: by 2002:a63:a35c:: with SMTP id v28mr18971322pgn.205.1548667677217; Mon, 28 Jan 2019 01:27:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548667677; cv=none; d=google.com; s=arc-20160816; b=0JEvlwnJwbTfL2Wzr1gBDAAaAjzcOwQ7iLcucr6qdwTZn8uClgT/+3Ir/mP9GKVK4V TOfSO8V/sgfYnmIT0SAvxeQt3kjjPe705yPSrKOt9JKG4C04rG/3y/z7MeDySM8aBTNy 2s0IhiZxtv9LLQVK+dbBMwjFL1Bu0Y29fwciJ4sPlleou3a3EYpTDawgbLYPL0auIo// OshwfNbhwSek684yiVabcSCaI6lyq7gbiLsMv5/vP1/vpqREOGBWh5Pfwq+uyftuhxzj dOkZ7f/qaeLZ2tLK52ZCUi7zvy+D2iQqxVAWatom4FFRNg+BUcFEiWL0JTucV1qIIaVw BeSA== 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; bh=IlfwZY6ZhoUWHNoO23uTG3L13UTI0WB7p9b/8ta2484=; b=VV2hPZaDwQOO+lbxWWc6HmIRqEI1awNKPvB34oaTedePUOfDHHr8RpH9j0XXvx/CTJ bhFhrKcU/qjuYSjhBxst/sTHRbkqWC2wMnycrYkzdftMQEzrBg607PEHvc16+9PkkrFY 8nkZXVB5LmYHS8G48hcPvRLEpU3q8qabz8iS9lhvqcpqnG480gP/zixQpDV/J+sbZNSG Xg6U47w6w4umo4TKno0+HlhKrs9eeDsjwB/BhXa6MT2ZKc94Xx3h1B6+FCfC1Xn0ku4h khgmbgjw1nhSVRk5jagWR0/x6h+4a4gxzHA3P5Mh/kAGBt30PLy35GwLt5wgAk/6ZE7y frhw== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k22si32090643pls.14.2019.01.28.01.27.41; Mon, 28 Jan 2019 01:27:57 -0800 (PST) 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726817AbfA1JZx (ORCPT + 99 others); Mon, 28 Jan 2019 04:25:53 -0500 Received: from mx2.suse.de ([195.135.220.15]:59910 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726369AbfA1JZw (ORCPT ); Mon, 28 Jan 2019 04:25:52 -0500 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 5DBDDAC5E; Mon, 28 Jan 2019 09:25:51 +0000 (UTC) Date: Mon, 28 Jan 2019 10:25:49 +0100 From: Michal Hocko To: Dan Williams Cc: Jane Chu , "Verma, Vishal L" , "Du, Fan" , "linux-kernel@vger.kernel.org" , "bp@suse.de" , "linux-mm@kvack.org" , "dave.hansen@linux.intel.com" , "tiwai@suse.de" , "akpm@linux-foundation.org" , "linux-nvdimm@lists.01.org" , "jglisse@redhat.com" , "zwisler@kernel.org" , "baiyaowei@cmss.chinamobile.com" , "thomas.lendacky@amd.com" , "Wu, Fengguang" , "Huang, Ying" , "bhelgaas@google.com" Subject: Re: [PATCH 5/5] dax: "Hotplug" persistent memory for use like normal RAM Message-ID: <20190128092549.GF18811@dhcp22.suse.cz> References: <20190124231441.37A4A305@viggo.jf.intel.com> <20190124231448.E102D18E@viggo.jf.intel.com> <0852310e-41dc-dc96-2da5-11350f5adce6@oracle.com> <5A90DA2E42F8AE43BC4A093BF067884825733A5B@SHSMSX104.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Fri 25-01-19 11:15:08, Dan Williams wrote: [...] > However, we should consider this along with the userspace enabling to > control which device-dax instances are set aside for hotplug. It would > make sense to have a "clear errors before hotplug" configuration > option. I am not sure I understand. Do you mean to clear HWPoison when the memory is hotadded (add_pages) or onlined (resp. move_pfn_range_to_zone)? -- Michal Hocko SUSE Labs