[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLXq=4dw=WfJZhXh=Ft3SHK1QUJZRt+rwy4ZuKTbjZUEpQ@mail.gmail.com>
Date: Mon, 4 Nov 2019 11:00:08 -0800
From: John Stultz <john.stultz@...aro.org>
To: Daniel Vetter <daniel@...ll.ch>
Cc: lkml <linux-kernel@...r.kernel.org>,
Sandeep Patil <sspatil@...gle.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Chenbo Feng <fengc@...gle.com>,
Alistair Strachan <astrachan@...gle.com>,
Liam Mark <lmark@...eaurora.org>, Yue Hu <huyue2@...ong.com>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"Andrew F . Davis" <afd@...com>,
Hridya Valsaraju <hridya@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Pratik Patel <pratikp@...eaurora.org>
Subject: Re: [RFC][PATCH 2/2] dma-buf: heaps: Allow system & cma heaps to be
configured as a modules
On Mon, Nov 4, 2019 at 2:24 AM Daniel Vetter <daniel@...ll.ch> wrote:
> On Fri, Oct 25, 2019 at 11:48:34PM +0000, John Stultz wrote:
> > Allow loading system and cma heap as a module instead of just as
> > a statically built in heap.
> >
> > Since there isn't a good mechanism for dmabuf lifetime tracking
> > it isn't safe to allow the heap drivers to be unloaded, so these
> > drivers do not implement any module unloading functionality and
> > will show up in lsmod as "[permanent]".
>
> dma-buf itself has all the try_module_get we'll need ... why is this not
> possible?
Let me look into that. Thanks for the pointer.
thanks
-john
Powered by blists - more mailing lists