* Luck, Tony <[email protected]> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
