Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-28 Thread Stephen Bates
Oliver >The alternative approach you mentioned that uses ioremap() should work >fine though. Great, thanks for this useful information Oliver. I am working on rebasing the ioremap() patch on 4.14 and will let you know how it goes. > Also, Alexy (+cc) said he was interested in trying this on s

Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-27 Thread Oliver
On Thu, Oct 26, 2017 at 1:34 AM, Oliver wrote: > On Tue, Oct 24, 2017 at 7:17 AM, Stephen Bates wrote: >> >>> [3.537780] lpar: Attempting to resize HPT to shift 21 >>> [3.539251] Unable to resize hash page table to target order 21: -1 >>> [3.541079] Unable to create mapping for hot a

Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-25 Thread Oliver
On Tue, Oct 24, 2017 at 7:17 AM, Stephen Bates wrote: > >> [3.537780] lpar: Attempting to resize HPT to shift 21 >> [3.539251] Unable to resize hash page table to target order 21: -1 >> [3.541079] Unable to create mapping for hot added memory >> 0xc0002100..0xc00021000400

Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-23 Thread Stephen Bates
> [3.537780] lpar: Attempting to resize HPT to shift 21 > [3.539251] Unable to resize hash page table to target order 21: -1 > [3.541079] Unable to create mapping for hot added memory > 0xc0002100..0xc00021000400: -2 > For #1 above please check if your qemu supports H_RES

Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-22 Thread Balbir Singh
On Sat, 21 Oct 2017 15:03:29 + "Stephen Bates" wrote: > > I am guessing that the hotplug of ZONE_DEVICE memory was done > > incorrectly as it lead to HPT resizing (the system thinking this is > > normal memory). Ideally one would expect that the driver would online > > ZONE_DEVICE memory and

Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-21 Thread Stephen Bates
> I am guessing that the hotplug of ZONE_DEVICE memory was done > incorrectly as it lead to HPT resizing (the system thinking this is > normal memory). Ideally one would expect that the driver would online > ZONE_DEVICE memory and not go through the HOTPLUG path. Are you using > devm_memremap_page

Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-17 Thread Balbir Singh
On Wed, Oct 18, 2017 at 7:38 AM, Stephen Bates wrote: > Hi All > > I am hoping someone can help shed some light on an issue I am seeing with my > attempt to add p2pmem [1] to the ppc64el kernel. p2pmem is a (currently) > out-of-tree patchset that allows one to add device memory with struct page

lpar issue for ZONE_DEVICE p2pmem in 4.14-rc

2017-10-17 Thread Stephen Bates
Hi All I am hoping someone can help shed some light on an issue I am seeing with my attempt to add p2pmem [1] to the ppc64el kernel. p2pmem is a (currently) out-of-tree patchset that allows one to add device memory with struct page backing into the Linux kernel. It leverages MEMORY_HOTPLUG and