[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 3/6] drm/i915: use vmap in shmem_pin_map
- To: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- From: Christoph Hellwig <hch@xxxxxx>
- Date: Tue, 22 Sep 2020 16:39:06 +0200
- Cc: Christoph Hellwig <hch@xxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx>, Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx>, Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx>, Minchan Kim <minchan@xxxxxxxxxx>, Nitin Gupta <ngupta@xxxxxxxxxx>, x86@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, intel-gfx@xxxxxxxxxxxxxxxxxxxxx, dri-devel@xxxxxxxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
- Delivery-date: Tue, 22 Sep 2020 14:39:18 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Tue, Sep 22, 2020 at 12:21:44PM +0100, Matthew Wilcox wrote:
> Actually, vfree() will work today; I cc'd you on a documentation update
> to make it clear that this is permitted.
vfree calls __free_pages, the i915 and a lot of other code calls
put_page. They are mostly the same, but not quite and everytime I
look into that mess I'm more confused than before.
Can someone in the know write sensible documentation on when to use
__free_page(s) vs put_page?
|
