Re: [GIT PULL] device-dax for 5.1: PMEM as RAM

2019-05-15 Thread Dan Williams
On Mon, Mar 11, 2019 at 5:08 PM Linus Torvalds wrote: > > On Mon, Mar 11, 2019 at 8:37 AM Dan Williams wrote: > > > > Another feature the userspace tooling can support for the PMEM as RAM > > case is the ability to complete an Address Range Scrub of the range > > before it is added to the core-mm

Re: [GIT PULL] device-dax for 5.1: PMEM as RAM

2019-03-11 Thread Dan Williams
On Mon, Mar 11, 2019 at 5:08 PM Linus Torvalds wrote: > > On Mon, Mar 11, 2019 at 8:37 AM Dan Williams wrote: > > > > Another feature the userspace tooling can support for the PMEM as RAM > > case is the ability to complete an Address Range Scrub of the range > > before it is added to the core-mm

Re: [GIT PULL] device-dax for 5.1: PMEM as RAM

2019-03-10 Thread Linus Torvalds
On Sun, Mar 10, 2019 at 4:54 PM Dan Williams wrote: > > Unfortunately this particular b0rkage is not constrained to nvmem. > I.e. there's nothing specific about nvmem requiring mc-safe memory > copy, it's a cpu problem consuming any poison regardless of > source-media-type with "rep; movs". So wh

Re: [GIT PULL] device-dax for 5.1: PMEM as RAM

2019-03-10 Thread Dan Williams
[ add Tony, who has wrestled with how to detect rep; movs recover-ability ] On Sun, Mar 10, 2019 at 1:02 PM Linus Torvalds wrote: > > On Sun, Mar 10, 2019 at 12:54 PM Dan Williams > wrote: > > > > Hi Linus, please pull from: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm

Re: [GIT PULL] device-dax for 5.1: PMEM as RAM

2019-03-10 Thread Linus Torvalds
On Sun, Mar 10, 2019 at 12:54 PM Dan Williams wrote: > > Hi Linus, please pull from: > > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm > tags/devdax-for-5.1 > > ...to receive new device-dax infrastructure to allow persistent memory > and other "reserved" / performance differentiate