From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 898ED1A236F for ; Fri, 15 Apr 2016 00:11:41 -0700 (PDT) From: Johannes Thumshirn Subject: Re: [PATCH] libnvdimm, pmem: clarify the write+clear_poison+write flow Date: Fri, 15 Apr 2016 09:11:39 +0200 Message-ID: <1569643.CdmplTuF3X@c203> In-Reply-To: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com> References: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com> MIME-Version: 1.0 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: linux-nvdimm@lists.01.org Cc: linux-kernel@vger.kernel.org List-ID: On Donnerstag, 14. April 2016 19:40:47 CEST Dan Williams wrote: > The ACPI specification does not specify the state of data after a clear > poison operation. Potential future libnvdimm bus implementations for > other architectures also might not specify or disagree on the state of > data after clear poison. Clarify why we write twice. > = > Reported-by: Jeff Moyer > Reported-by: Vishal Verma > Signed-off-by: Dan Williams > --- Reviewed-by: Johannes Thumshirn -- = Johannes Thumshirn = Storage jthumshirn@suse.de = +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N=FCrnberg GF: Felix Imend=F6rffer, Jane Smithard, Graham Norton HRB 21284 (AG N=FCrnberg) Key fingerprint =3D EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753370AbcDOHLm (ORCPT ); Fri, 15 Apr 2016 03:11:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:45329 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753271AbcDOHLl convert rfc822-to-8bit (ORCPT ); Fri, 15 Apr 2016 03:11:41 -0400 From: Johannes Thumshirn To: linux-nvdimm@ml01.01.org Cc: Dan Williams , linux-kernel@vger.kernel.org Subject: Re: [PATCH] libnvdimm, pmem: clarify the write+clear_poison+write flow Date: Fri, 15 Apr 2016 09:11:39 +0200 Message-ID: <1569643.CdmplTuF3X@c203> User-Agent: KMail/5.1.3 (Linux/4.5.0-3-default; KDE/5.20.0; x86_64; ; ) In-Reply-To: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com> References: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Donnerstag, 14. April 2016 19:40:47 CEST Dan Williams wrote: > The ACPI specification does not specify the state of data after a clear > poison operation. Potential future libnvdimm bus implementations for > other architectures also might not specify or disagree on the state of > data after clear poison. Clarify why we write twice. > > Reported-by: Jeff Moyer > Reported-by: Vishal Verma > Signed-off-by: Dan Williams > --- Reviewed-by: Johannes Thumshirn -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850