* Dan Williams wrote:
> [ adding nvdimm folks ]
>
> On Fri, Nov 27, 2015 at 2:16 AM, Ingo Molnar wrote:
> >
> > * Luck, Tony 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,
> >> > > +
> 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.
I'm making a V2 that fixes some build errors
[ adding nvdimm folks ]
On Fri, Nov 27, 2015 at 2:16 AM, Ingo Molnar wrote:
>
> * Luck, Tony 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);
>> >
* Luck, Tony 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 i
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
* Tony Luck wrote:
> Using __copy_user_nocache() as inspiration create a memory copy
> routine for use by kernel code with annotations to allow for
> recovery from machine checks.
>
> Notes:
> 1) Unlike the original we make no attempt to copy all the bytes
>up to the faulting address. The o
6 matches
Mail list logo
