[ adding akpm, sfr, and jens ]
I applied this series and pushed it out for the nvdimm.git branch that
gets auto pulled into -next. The set is still awaiting acks from
device-mapper, ext4, xfs, and vfs (for the copy_from_iter_ops, patch
29/33). If those come next week perhaps this can be merged for
The nvdimm_flush() mechanism helps to reduce the impact of an ADR
(asynchronous-dimm-refresh) failure. The ADR mechanism handles flushing
platform WPQ (write-pending-queue) buffers when power is removed. The
nvdimm_flush() mechanism performs that same function on-demand.
When a pmem namespace is a
On Thu, 2017-04-13 at 13:31 +0200, Borislav Petkov wrote:
> On Thu, Apr 13, 2017 at 12:29:25AM +0200, Borislav Petkov wrote:
> > On Wed, Apr 12, 2017 at 03:26:19PM -0700, Luck, Tony wrote:
> > > We can futz with that and have them specify which chain (or both)
> > > that they want to be added to.
>
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Fri, Apr 21, 2017 at 01:27:41PM -0700, Luck, Tony wrote:
> Boris: you coded up a "static bool memory_error(struct mce *m)"
> function inside the patches for the corrected error thingy.
>
> Perhaps when it goes upstream it should be available for other
> users too?
I don't see why not. struct m
On 04/21, Luck, Tony wrote:
> On Fri, Apr 21, 2017 at 02:35:51PM -0600, Vishal Verma wrote:
> > On 04/21, Luck, Tony wrote:
> > > Needs extra parentheses to make it right. Vishal, sorry I led you astray.
> > >
> > > if (!((mce->status & 0xef80) == BIT(7)))
> >
> > Is this still right though? An
On Fri, Apr 21, 2017 at 02:35:51PM -0600, Vishal Verma wrote:
> On 04/21, Luck, Tony wrote:
> > Needs extra parentheses to make it right. Vishal, sorry I led you astray.
> >
> > if (!((mce->status & 0xef80) == BIT(7)))
>
> Is this still right though? Anything AND'ed with 0xef80 will never equ
On 04/21, Luck, Tony wrote:
> >> > + if (!(mce->status & 0xef80) == BIT(7))
> >>
> >> Can we get a define for this, or a comment explaining all the magic
> >> that's happening on that one line?
> >
> > Yes - also like lkp pointed out, the check isn't correct at all. Let me
> > figure out wha
On Fri, Apr 21, 2017 at 01:19:16PM -0700, Dan Williams wrote:
> On Fri, Apr 21, 2017 at 1:16 PM, Luck, Tony wrote:
> >>> > + if (!(mce->status & 0xef80) == BIT(7))
> >>>
> >>> Can we get a define for this, or a comment explaining all the magic
> >>> that's happening on that one line?
> >>
>
On Fri, Apr 21, 2017 at 1:16 PM, Luck, Tony wrote:
>>> > + if (!(mce->status & 0xef80) == BIT(7))
>>>
>>> Can we get a define for this, or a comment explaining all the magic
>>> that's happening on that one line?
>>
>> Yes - also like lkp pointed out, the check isn't correct at all. Let me
>
>> > + if (!(mce->status & 0xef80) == BIT(7))
>>
>> Can we get a define for this, or a comment explaining all the magic
>> that's happening on that one line?
>
> Yes - also like lkp pointed out, the check isn't correct at all. Let me
> figure out what really needs to be done, and I will rese
On Fri, 2017-04-21 at 12:21 -0700, Dan Williams wrote:
> On Thu, Apr 20, 2017 at 3:18 PM, Vishal Verma m> wrote:
> > The check for an MCE being a memory error in the NFIT mce handler
> > was
> > bogus. Fix it to check for the correct MCA status compound error
> > code.
> >
> > Reported-by: Tony L
On Thu, Apr 20, 2017 at 3:18 PM, Vishal Verma wrote:
> The check for an MCE being a memory error in the NFIT mce handler was
> bogus. Fix it to check for the correct MCA status compound error code.
>
> Reported-by: Tony Luck
> Cc:
> Signed-off-by: Vishal Verma
> ---
> drivers/acpi/nfit/mce.c |
详 情 请 查 阅 附 件 大 纲
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Fri, Apr 21, 2017 at 12:12 AM, Oliver O'Halloran wrote:
> Print the alignment for dax namespaces creation. It's good to be explicit
> about
> it since about the selected region alignment dictates the type of faults
> we allow on the namespace.
>
> Signed-off-by: Oliver O'Halloran
> ---
> uti
On Fri, Apr 21, 2017 at 12:12 AM, Oliver O'Halloran wrote:
> These are needed on powerpc since 64K is the default page size and 16MB
> is the PMD size when using the hash MMU.
>
> Signed-off-by: Oliver O'Halloran
> ---
> ndctl/builtin-xaction-namespace.c | 2 ++
> util/size.h
On Fri, Apr 21, 2017 at 12:12 AM, Oliver O'Halloran wrote:
> Read the default alignment from the hpage_pmd_size in sysfs. On PPC the
> PMD size depends on the MMU being used. When the traditional hash MMU is
> used (P9 and earlier) the PMD size is 16MB while the newer radix MMU
> uses a 2MB PMD si
These are needed on powerpc since 64K is the default page size and 16MB
is the PMD size when using the hash MMU.
Signed-off-by: Oliver O'Halloran
---
ndctl/builtin-xaction-namespace.c | 2 ++
util/size.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/ndctl/builtin-xa
Read the default alignment from the hpage_pmd_size in sysfs. On PPC the
PMD size depends on the MMU being used. When the traditional hash MMU is
used (P9 and earlier) the PMD size is 16MB while the newer radix MMU
uses a 2MB PMD size. The choice of MMU is done at runtime depending on
what the hardw
Print the alignment for dax namespaces creation. It's good to be explicit about
it since about the selected region alignment dictates the type of faults
we allow on the namespace.
Signed-off-by: Oliver O'Halloran
---
util/json.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/util/json.
20 matches
Mail list logo
