On Tue, 2018-12-04 at 11:08 -0800, Dan Williams wrote: > On Mon, Dec 3, 2018 at 1:50 PM Alexander Duyck > <alexander.h.duyck@xxxxxxxxxxxxxxx> wrote: > > > > On Mon, 2018-12-03 at 13:05 -0800, Dan Williams wrote: > > > On Mon, Dec 3, 2018 at 12:53 PM Alexander Duyck > > > <alexander.h.duyck@xxxxxxxxxxxxxxx> wrote: > > > > > > > > On Mon, 2018-12-03 at 12:31 -0800, Dan Williams wrote: > > > > > On Mon, Dec 3, 2018 at 12:21 PM Alexander Duyck > > > > > <alexander.h.duyck@xxxxxxxxxxxxxxx> wrote: > > > > > > > > > > > > On Mon, 2018-12-03 at 11:47 -0800, Dan Williams wrote: > > > > > > > On Mon, Dec 3, 2018 at 11:25 AM Alexander Duyck > > > > > > > <alexander.h.duyck@xxxxxxxxxxxxxxx> wrote: > > > > > > > > > > > > > > > > Add a means of exposing if a pagemap supports refcount pinning. I am doing > > > > > > > > this to expose if a given pagemap has backing struct pages that will allow > > > > > > > > for the reference count of the page to be incremented to lock the page > > > > > > > > into place. > > > > > > > > > > > > > > > > The KVM code already has several spots where it was trying to use a > > > > > > > > pfn_valid check combined with a PageReserved check to determien if it could > > > > > > > > take a reference on the page. I am adding this check so in the case of the > > > > > > > > page having the reserved flag checked we can check the pagemap for the page > > > > > > > > to determine if we might fall into the special DAX case. > > > > > > > > > > > > > > > > Signed-off-by: Alexander Duyck <alexander.h.duyck@xxxxxxxxxxxxxxx> > > > > > > > > --- > > > > > > > > drivers/nvdimm/pfn_devs.c | 2 ++ > > > > > > > > include/linux/memremap.h | 5 ++++- > > > > > > > > include/linux/mm.h | 11 +++++++++++ > > > > > > > > 3 files changed, 17 insertions(+), 1 deletion(-) > > > > > > > > > > > > > > > > diff --git a/drivers/nvdimm/pfn_devs.c b/drivers/nvdimm/pfn_devs.c > > > > > > > > index 6f22272e8d80..7a4a85bcf7f4 100644 > > > > > > > > --- a/drivers/nvdimm/pfn_devs.c > > > > > > > > +++ b/drivers/nvdimm/pfn_devs.c > > > > > > > > @@ -640,6 +640,8 @@ static int __nvdimm_setup_pfn(struct nd_pfn *nd_pfn, struct dev_pagemap *pgmap) > > > > > > > > } else > > > > > > > > return -ENXIO; > > > > > > > > > > > > > > > > + pgmap->support_refcount_pinning = true; > > > > > > > > + > > > > > > > > > > > > > > There should be no dev_pagemap instance instance where this isn't > > > > > > > true, so I'm missing why this is needed? > > > > > > > > > > > > I thought in the case of HMM there were instances where you couldn't > > > > > > pin the page, isn't there? Specifically I am thinking of the definition > > > > > > of MEMORY_DEVICE_PUBLIC: > > > > > > Device memory that is cache coherent from device and CPU point of > > > > > > view. This is use on platform that have an advance system bus (like > > > > > > CAPI or CCIX). A driver can hotplug the device memory using > > > > > > ZONE_DEVICE and with that memory type. Any page of a process can be > > > > > > migrated to such memory. However no one should be allow to pin such > > > > > > memory so that it can always be evicted. > > > > > > > > > > > > It sounds like MEMORY_DEVICE_PUBLIC and MMIO would want to fall into > > > > > > the same category here in order to allow a hot-plug event to remove the > > > > > > device and take the memory with it, or is my understanding on this not > > > > > > correct? > > > > > > > > > > I don't understand how HMM expects to enforce no pinning, but in any > > > > > event it should always be the expectation an elevated reference count > > > > > on a page prevents that page from disappearing. Anything else is > > > > > broken. > > > > > > > > I don't think that is true for device MMIO though. > > > > > > > > In the case of MMIO you have the memory region backed by a device, if > > > > that device is hot-plugged or fails in some way then that backing would > > > > go away and the reads would return and all 1's response. > > > > > > Until p2pdma there are no struct pages for device memory, is that what > > > you're referring? > > > > Honestly I am not sure. It is possible I am getting beyond my depth. > > > > My understanding is that we have a 'struct page' for any of these pages > > that we are currently using. It is just a matter of if we want to pass > > the struct page around or not. So for example in the case of an MMIO > > page we still have a 'struct page', however the PG_reserved flag is set > > on such a page, so KVM is opting to not touch the reference count, > > modify the dirty/accessed bits, and is generally reducing performance > > as a result. > > > > > Otherwise any device driver that leaks "struct pages" into random code > > > paths in the kernel had better not expect to be able to > > > surprise-remove those pages from the system. Any dev_pagemap user > > > should expect to do a coordinated removal with the driver that waits > > > for page references to drop before the device can be physically > > > removed. > > > > Right. This part I get. However I would imagine there still has to be > > some exception handling in the case of a PCIe backed region of memory > > so that if the device falls of the bus we clean up the dev_pagemap > > memory. > > There isn't. This is a gap. Persistent memory gets around this by the > fact that none of the current NVDIMM bus implementations support > surprise physical unplug. HMM may be broken in this regard when GPUs > fall of the bus, but I don't think this is a recoverable situation > once applications have been handed direct access to the memory > resource. There is no recovery without a device-driver intermediary to > gracefully fail transactions. > > > > > Holding a reference to the page doesn't guarantee that the backing > > > > device cannot go away. > > > > > > Correct there is no physical guarantee, but that's not the point. It > > > needs to be coordinated, otherwise all bets are off with respect to > > > system stability. > > > > Right. > > > > > > I believe that is the origin of the original use > > > > of the PageReserved check in KVM in terms of if it will try to use the > > > > get_page/put_page functions. > > > > > > Is it? MMIO does not typically have a corresponding 'struct page'. > > > > I think we might be talking about different things when we say 'struct > > page'. I'm pretty sure there has to be a 'struct page' for the MMIO > > region as otherwise we wouldn't be able to check for the PG_reserved > > bit in the 'struct page'. Do you maybe mean that MMIO doesn't have a > > corresponding virtual address or TLB entry? > > No. > > > I know that is what we are > > normally generating via the ioremap family of calls in device drivers > > in order to access such memory if I am not mistaken. > > I think the confusion arises from the fact that there are a few MMIO > resources with a struct page and all the rest MMIO resources without. > The problem comes from the coarse definition of pfn_valid(), it may > return 'true' for things that are not System-RAM, because pfn_valid() > may be something as simplistic as a single "address < X" check. Then > PageReserved is a fallback to clarify the pfn_valid() result. The > typical case is that MMIO space is not caught up in this linear map > confusion. An MMIO address may or may not have an associated 'struct > page' and in most cases it does not. Okay. I think I understand this somewhat now. So the page might be physically there, but with the reserved bit it is not supposed to be touched. My main concern with just dropping the bit is that we start seeing some other uses that I was not certain what the impact would be. For example the functions like kvm_set_pfn_accessed start going in and manipulating things that I am not sure should be messed with for a DAX page. > > > > I believe this is also why > > > > MEMORY_DEVICE_PUBLIC specifically calls out that you should not allow > > > > pinning such memory. > > > > > > I don't think that call out was referencing device hotplug, I believe > > > it was the HMM expectation that it should be able to move an HMM page > > > from device to System-RAM at will. > > > > I could be wrong. If so that would make this patch set easier since > > essentially it would just mean that any PageReserved page that matches > > is_zone_device_page would fall into this category then and I could just > > drop patch 2, and probably combine the entire fix for all of this into > > one patch as it would only really be a few additional lines. > > > > I took another look at PageReserved usage, I really think we're better > off just deleting PageReserved for dax and fixing up the small number > of places where it matters. By my count there are only 44 tests for > PageReserved and most of those are locations that would never see a > dax page. Right. The thing I am worried about is the cascade of secondary effects that start kicking in because of us not setting the PageReserved bit. So for example kvm_set_pfn_accessed can call mark_page_accessed. That in turn takes a few calls to get into any issues as the first call will leave the page as inactive, and set the referenced flag. The second call to it is supposed to set the active flag but I am assuming that won't happen due to the fact that we aren't supposed to touch LRU. However, we are not a swap backed page so I suspect we will go through workingset_activation() and I am not sure what the impact there will be since I don't believe we have a memory cgroup associated with the DAX pages do we?
