From: Johannes Thumshirn <jthumshirn@suse.de>
To: linux-nvdimm@lists.01.org
Cc: 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 [thread overview]
Message-ID: <1569643.CdmplTuF3X@c203> (raw)
In-Reply-To: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com>
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 <jmoyer@redhat.com>
> Reported-by: Vishal Verma <vishal.l.verma@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
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
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de>
To: linux-nvdimm@ml01.01.org
Cc: Dan Williams <dan.j.williams@intel.com>, 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 [thread overview]
Message-ID: <1569643.CdmplTuF3X@c203> (raw)
In-Reply-To: <146068804768.24085.7722589204633361307.stgit@dwillia2-desk3.jf.intel.com>
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 <jmoyer@redhat.com>
> Reported-by: Vishal Verma <vishal.l.verma@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
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
next prev parent reply other threads:[~2016-04-15 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 2:40 [PATCH] libnvdimm, pmem: clarify the write+clear_poison+write flow Dan Williams
2016-04-15 2:40 ` Dan Williams
2016-04-15 7:11 ` Johannes Thumshirn [this message]
2016-04-15 7:11 ` Johannes Thumshirn
2016-04-15 12:32 ` Jeff Moyer
2016-04-15 16:58 ` Verma, Vishal L
2016-04-15 16:58 ` Verma, Vishal L
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1569643.CdmplTuF3X@c203 \
--to=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.