Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1291025 > unrolled thread
| Started by | Ingo Molnar <mingo@kernel.org> |
|---|---|
| First post | 2015-12-14 11:00 +0100 |
| Last post | 2015-12-14 11:00 +0100 |
| Articles | 1 — 1 participant |
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.
Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks Ingo Molnar <mingo@kernel.org> - 2015-12-14 11:00 +0100
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Date | 2015-12-14 11:00 +0100 |
| Subject | Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks |
| Message-ID | <qFy5c-4ms-17@gated-at.bofh.it> |
* Dan Williams <dan.j.williams@intel.com> wrote: > [ 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. So there was some feedback for v2 as well - I'd like to see v3 before an Acked-by. But yeah, this is progressing in the right direction, and I suspect it's a relatively urgent feature from an nvdimm POV? Thanks, Ingo -- 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/
Back to top | Article view | linux.kernel
csiph-web