Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7398299imu; Mon, 3 Dec 2018 12:14:43 -0800 (PST) X-Google-Smtp-Source: AFSGD/Uv9dJlHMrv+UjQZEFyHLo8CF7UwoHdytoU1WEmgKqPYlrqwi+36indPoR2aFV+iDrN6Il5 X-Received: by 2002:a17:902:29a7:: with SMTP id h36mr17487968plb.244.1543868083778; Mon, 03 Dec 2018 12:14:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543868083; cv=none; d=google.com; s=arc-20160816; b=EjN9T6Ry2xxIvYdau6qTt5i6gI6ufpT6Pe9u+y5FXxhpJ7RoEi5CQAFmYQ1DQTRXSc cklJ3lBHRXrG4UwdiO+6DGjP1x+91GbT3HNUXXGNuDPfF+oPCv6Sq5gQBePkZPgXZBs8 0JaqoQBkiicgpMVN+57ITju1Gsw/SPyLoykNtbmfHWTstT+9Yjyn2TSL4IKISGmR3YI4 /LCIfczqfnoS9mu4xM3LjwG2DnuM3MoxGcOR/mkUCK6HWg00OVw5/LETGJMjYskT4rCF s5w0S+VlM2Wtwr9DfYTh+B7TEMVG+aZdpgErlGHhpzf8D7TlJjXNIqragSbZDhRNaFRa bkSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=AC8NroRJRLErebhHuSWdZY1XtwOPkgi7PHPjmk1XnzM=; b=ksVvKwoCxRqt3GWtySDuqvkm6E0/p9/KXVzGXwUxVRmA/dzOCf8kWMns9oOl6IVZej n9IeRGISKSDM1OOZlPYLfxreN8snW7VhkaHC0Bol3lU0BeVTX9qPcNs5NGX4664NfsTX VdgdDfFeDGGNzWy0v/8052P9mlblUDHpLyoigziVHBVybRLanHEN+JGolDlhiBPgVjWx Cdnm3i3y4FdGBSfTfxzzJWHMG1pGgbQovXKnhunhpktpJsyVdA8dlgcwVhuH2vFBwrFw +yHaV39tvikGzSwaGX1WlgtXZWFT6OezHY0NEFVFjpzWIfQ86llnHDbIqiyxBH6GZhIt NeDQ== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j65si13490320pge.444.2018.12.03.12.14.26; Mon, 03 Dec 2018 12:14:43 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726044AbeLCUM1 (ORCPT + 99 others); Mon, 3 Dec 2018 15:12:27 -0500 Received: from mga05.intel.com ([192.55.52.43]:18155 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725913AbeLCUM1 (ORCPT ); Mon, 3 Dec 2018 15:12:27 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2018 12:12:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,311,1539673200"; d="scan'208";a="106963995" Received: from djiang5-mobl2.amr.corp.intel.com (HELO [10.254.190.169]) ([10.254.190.169]) by orsmga003.jf.intel.com with ESMTP; 03 Dec 2018 12:12:25 -0800 Subject: Re: [PATCH] acpi/nfit: Fix user-initiated ARS to be "ARS-long" rather than "ARS-short" To: Dan Williams , linux-nvdimm@lists.01.org Cc: Jacek Zloch , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org References: <154386182529.24428.16722249724563229676.stgit@dwillia2-desk3.amr.corp.intel.com> From: Dave Jiang Message-ID: <6345bd3b-b5c0-eb51-bd81-878cd764e66d@intel.com> Date: Mon, 3 Dec 2018 13:12:24 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:64.0) Gecko/20100101 Thunderbird/64.0 MIME-Version: 1.0 In-Reply-To: <154386182529.24428.16722249724563229676.stgit@dwillia2-desk3.amr.corp.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/3/2018 11:30 AM, Dan Williams wrote: > A "short" ARS (address range scrub) instructs the platform firmware to > return known errors. In contrast, a "long" ARS instructs platform > firmware to arrange every data address on the DIMM to be read / checked > for poisoned data. > > The conversion of the flags in commit d3abaf43bab8 "acpi, nfit: Fix > Address Range Scrub completion tracking", changed the meaning of passing > '0' to acpi_nfit_ars_rescan(). Previously '0' meant "not short", now '0' > is ARS_REQ_SHORT. Pass ARS_REQ_LONG to restore the expected scrub-type > behavior of user-initiated ARS sessions. > > Fixes: d3abaf43bab8 ("acpi, nfit: Fix Address Range Scrub completion tracking") > Reported-by: Jacek Zloch > Cc: Vishal Verma > Signed-off-by: Dan Williams Reviewed-by: Dave Jiang > --- > drivers/acpi/nfit/core.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c > index 14d9f5bea015..5912d30020c7 100644 > --- a/drivers/acpi/nfit/core.c > +++ b/drivers/acpi/nfit/core.c > @@ -1308,7 +1308,7 @@ static ssize_t scrub_store(struct device *dev, > if (nd_desc) { > struct acpi_nfit_desc *acpi_desc = to_acpi_desc(nd_desc); > > - rc = acpi_nfit_ars_rescan(acpi_desc, 0); > + rc = acpi_nfit_ars_rescan(acpi_desc, ARS_REQ_LONG); > } > device_unlock(dev); > if (rc) > > _______________________________________________ > Linux-nvdimm mailing list > Linux-nvdimm@lists.01.org > https://lists.01.org/mailman/listinfo/linux-nvdimm