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-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-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

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

Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations

2017-06-22 Thread Stephen Bates
> +#define iowrite64be(v,p) iowrite32(cpu_to_be64(v), (p)) Logan, thanks for taking this cleanup on. I think this should be iowrite64 not iowrite32? Stephen