Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1286863 > unrolled thread

Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks

Started byDan Williams <dan.j.williams@intel.com>
First post2015-12-08 22:40 +0100
Last post2015-12-08 23:10 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover  from machine checks Dan Williams <dan.j.williams@intel.com> - 2015-12-08 22:40 +0100
    RE: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover  from machine checks "Luck, Tony" <tony.luck@intel.com> - 2015-12-08 23:10 +0100

#1286863 — Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks

FromDan Williams <dan.j.williams@intel.com>
Date2015-12-08 22:40 +0100
SubjectRe: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks
Message-ID<qDy9k-7FQ-11@gated-at.bofh.it>
[ adding nvdimm folks ]

On Fri, Nov 27, 2015 at 2:16 AM, Ingo Molnar <mingo@kernel.org> wrote:
>
> * Luck, Tony <tony.luck@intel.com> wrote:
>
>> On Thu, Nov 12, 2015 at 08:53:13AM +0100, Ingo Molnar wrote:
>> > > +extern phys_addr_t mcsafe_memcpy(void *dst, const void __user *src,
>> > > +                         unsigned size);
>> >
>> > So what's the longer term purpose, where will mcsafe_memcpy() be used?
>>
>> The initial plan is to use this for file systems backed by NVDIMMs. They will
>> have a large amount of memory, and we have a practical recovery path - return
>> -EIO just like legacy h/w.
>>
>> We can look for other places in the kernel where we read large amounts of memory
>> and have some idea how to recover if the memory turns out to be bad.
>
> I see, that's sensible!
>
> Thanks,
>
>         Ingo

Is that an "Acked-by"?  I'd like to pull this plus Vishal's
gendisk-badblocks patches into a unified libnvdimm-error-handling
branch.  We're looking to have v4.5 able to avoid or survive nvdimm
media errors through the pmem driver and DAX paths.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1286880

From"Luck, Tony" <tony.luck@intel.com>
Date2015-12-08 23:10 +0100
Message-ID<qDyCl-85p-5@gated-at.bofh.it>
In reply to#1286863
PiBJcyB0aGF0IGFuICJBY2tlZC1ieSI/ICBJJ2QgbGlrZSB0byBwdWxsIHRoaXMgcGx1cyBWaXNo
YWwncw0KPiBnZW5kaXNrLWJhZGJsb2NrcyBwYXRjaGVzIGludG8gYSB1bmlmaWVkIGxpYm52ZGlt
bS1lcnJvci1oYW5kbGluZw0KPiBicmFuY2guICBXZSdyZSBsb29raW5nIHRvIGhhdmUgdjQuNSBh
YmxlIHRvIGF2b2lkIG9yIHN1cnZpdmUgbnZkaW1tDQo+IG1lZGlhIGVycm9ycyB0aHJvdWdoIHRo
ZSBwbWVtIGRyaXZlciBhbmQgREFYIHBhdGhzLg0KDQpJJ20gbWFraW5nIGEgVjIgdGhhdCBmaXhl
cyBzb21lIGJ1aWxkIGVycm9ycyBmb3IgMzItYml0IGFuZCBhZGRyZXNzZXMgb3RoZXIgY29tbWVu
dGFyeQ0KZnJvbSB0aGUgY29tbXVuaXR5LiBQZXJoYXBzIGEgY291cGxlIG1vcmUgZGF5cyBiZWZv
cmUgSSBmaW5pc2ggaXQgdXAgcmVhZHkgdG8gcG9zdC4NCg0KLVRvbnkNCg==
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web