On 06.10.20 08:55, Dan Williams wrote: > Towards removing the mode specific @dax_kmem_res attribute from the > generic 'struct dev_dax', and preparing for multi-range support, move > resource tracking to driver data. The memory for the resource name > needs to have its own lifetime separate from the device bind lifetime > for cases where the driver is unbound, but the kmem range could not be > unplugged from the page allocator. > > The resource reservation also needs to be released manually via > release_resource() given the awkward manipulation of the > IORESOURCE_BUSY flag. > > Cc: David Hildenbrand <[email protected]> > Cc: Vishal Verma <[email protected]> > Cc: Dave Hansen <[email protected]> > Cc: Pavel Tatashin <[email protected]> > Cc: Brice Goglin <[email protected]> > Cc: Dave Jiang <[email protected]> > Cc: David Hildenbrand <[email protected]> > Cc: Ira Weiny <[email protected]> > Cc: Jia He <[email protected]> > Cc: Joao Martins <[email protected]> > Cc: Jonathan Cameron <[email protected]> > Signed-off-by: Dan Williams <[email protected]>
Reviewed-by: David Hildenbrand <[email protected]> Thanks! -- Thanks, David / dhildenb
