Re: [PATCH v2] drm/gem: Fix mmap fake offset handling for drm_gem_object_funcs.mmap

Hi,

...

I can see now why you want a private address space for each object. Does that imply we need an anon_inode for each gem object? Or is there some more lightweight way to do this?

I have no idea whether we can get a address_space struct without an inode (and no disasters).

Anything building on shmem helpers should be able to use obj->filp->f_mapping, right? So allocating an inode unconditionally doesn't look like a good plan.

Guess I'll go look at ttm-local changes for starters and see how it goes.

cheers, Gerd