From: Christoph Hellwig <hch@lst.de> To: Andrew Morton <akpm@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Juergen Gross <jgross@suse.com>, Stefano Stabellini <sstabellini@kernel.org>, Jani Nikula <jani.nikula@linux.intel.com>, Joonas Lahtinen <joonas.lahtinen@linux.intel.com>, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>, Chris Wilson <chris@chris-wilson.co.uk>, Matthew Auld <matthew.auld@intel.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>, Minchan Kim <minchan@kernel.org>, Matthew Wilcox <willy@infradead.org>, Nitin Gupta <ngupta@vflare.org>, x86@kernel.org, xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-mm@kvack.org Subject: remove alloc_vm_area v4 Date: Fri, 2 Oct 2020 14:21:53 +0200 [thread overview] Message-ID: <20201002122204.1534411-1-hch@lst.de> (raw) Hi Andrew, this series removes alloc_vm_area, which was left over from the big vmalloc interface rework. It is a rather arkane interface, basicaly the equivalent of get_vm_area + actually faulting in all PTEs in the allocated area. It was originally addeds for Xen (which isn't modular to start with), and then grew users in zsmalloc and i915 which seems to mostly qualify as abuses of the interface, especially for i915 as a random driver should not set up PTE bits directly. A git tree is also available here: git://git.infradead.org/users/hch/misc.git alloc_vm_area Gitweb: http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/alloc_vm_area Changes since v2: - rebased to include the two conflicting i915 changes in drm-tip / linux-next again. No changes outside of drivers/gpu/drm/i915/ Changes since v2: - add another missing i initialization - rebased to mainline instead of drm-tip again Changes since v1: - fix a bug in the zsmalloc changes - fix a bug and rebase to include the recent changes in i915 - add a new vmap flag that allows to free the page array and pages using vfree - add a vfree documentation updated from Matthew Diffstat: arch/x86/xen/grant-table.c | 27 ++++-- drivers/gpu/drm/i915/Kconfig | 1 drivers/gpu/drm/i915/gem/i915_gem_pages.c | 131 +++++++++++++----------------- drivers/gpu/drm/i915/gt/shmem_utils.c | 76 ++++------------- drivers/xen/xenbus/xenbus_client.c | 30 +++--- include/linux/vmalloc.h | 7 - mm/Kconfig | 3 mm/memory.c | 16 ++- mm/nommu.c | 7 - mm/vmalloc.c | 123 ++++++++++++++-------------- mm/zsmalloc.c | 10 +- 11 files changed, 200 insertions(+), 231 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Andrew Morton <akpm@linux-foundation.org> Cc: Juergen Gross <jgross@suse.com>, Stefano Stabellini <sstabellini@kernel.org>, Matthew Wilcox <willy@infradead.org>, dri-devel@lists.freedesktop.org, linux-mm@kvack.org, Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, x86@kernel.org, Chris Wilson <chris@chris-wilson.co.uk>, Minchan Kim <minchan@kernel.org>, Matthew Auld <matthew.auld@intel.com>, xen-devel@lists.xenproject.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Nitin Gupta <ngupta@vflare.org> Subject: [Intel-gfx] remove alloc_vm_area v4 Date: Fri, 2 Oct 2020 14:21:53 +0200 [thread overview] Message-ID: <20201002122204.1534411-1-hch@lst.de> (raw) Hi Andrew, this series removes alloc_vm_area, which was left over from the big vmalloc interface rework. It is a rather arkane interface, basicaly the equivalent of get_vm_area + actually faulting in all PTEs in the allocated area. It was originally addeds for Xen (which isn't modular to start with), and then grew users in zsmalloc and i915 which seems to mostly qualify as abuses of the interface, especially for i915 as a random driver should not set up PTE bits directly. A git tree is also available here: git://git.infradead.org/users/hch/misc.git alloc_vm_area Gitweb: http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/alloc_vm_area Changes since v2: - rebased to include the two conflicting i915 changes in drm-tip / linux-next again. No changes outside of drivers/gpu/drm/i915/ Changes since v2: - add another missing i initialization - rebased to mainline instead of drm-tip again Changes since v1: - fix a bug in the zsmalloc changes - fix a bug and rebase to include the recent changes in i915 - add a new vmap flag that allows to free the page array and pages using vfree - add a vfree documentation updated from Matthew Diffstat: arch/x86/xen/grant-table.c | 27 ++++-- drivers/gpu/drm/i915/Kconfig | 1 drivers/gpu/drm/i915/gem/i915_gem_pages.c | 131 +++++++++++++----------------- drivers/gpu/drm/i915/gt/shmem_utils.c | 76 ++++------------- drivers/xen/xenbus/xenbus_client.c | 30 +++--- include/linux/vmalloc.h | 7 - mm/Kconfig | 3 mm/memory.c | 16 ++- mm/nommu.c | 7 - mm/vmalloc.c | 123 ++++++++++++++-------------- mm/zsmalloc.c | 10 +- 11 files changed, 200 insertions(+), 231 deletions(-) _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-10-02 12:22 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-02 12:21 Christoph Hellwig [this message] 2020-10-02 12:21 ` [Intel-gfx] remove alloc_vm_area v4 Christoph Hellwig 2020-10-02 12:21 ` [PATCH 01/11] mm: update the documentation for vfree Christoph Hellwig 2020-10-02 12:21 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:21 ` [PATCH 02/11] mm: add a VM_MAP_PUT_PAGES flag for vmap Christoph Hellwig 2020-10-02 12:21 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:21 ` [PATCH 03/11] mm: add a vmap_pfn function Christoph Hellwig 2020-10-02 12:21 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:21 ` [PATCH 04/11] mm: allow a NULL fn callback in apply_to_page_range Christoph Hellwig 2020-10-02 12:21 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:21 ` [PATCH 05/11] zsmalloc: switch from alloc_vm_area to get_vm_area Christoph Hellwig 2020-10-02 12:21 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:21 ` [PATCH 06/11] drm/i915: use vmap in shmem_pin_map Christoph Hellwig 2020-10-02 12:21 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:22 ` [PATCH 07/11] drm/i915: stop using kmap in i915_gem_object_map Christoph Hellwig 2020-10-02 12:22 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:22 ` [PATCH 08/11] drm/i915: use vmap " Christoph Hellwig 2020-10-02 12:22 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:22 ` [PATCH 09/11] xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv Christoph Hellwig 2020-10-02 12:22 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:22 ` [PATCH 10/11] x86/xen: open code alloc_vm_area in arch_gnttab_valloc Christoph Hellwig 2020-10-02 12:22 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:22 ` [PATCH 11/11] mm: remove alloc_vm_area Christoph Hellwig 2020-10-02 12:22 ` [Intel-gfx] " Christoph Hellwig 2020-10-02 12:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] mm: update the documentation for vfree Patchwork 2020-10-02 12:59 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201002122204.1534411-1-hch@lst.de \ --to=hch@lst.de \ --cc=akpm@linux-foundation.org \ --cc=boris.ostrovsky@oracle.com \ --cc=chris@chris-wilson.co.uk \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jani.nikula@linux.intel.com \ --cc=jgross@suse.com \ --cc=joonas.lahtinen@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=matthew.auld@intel.com \ --cc=minchan@kernel.org \ --cc=ngupta@vflare.org \ --cc=peterz@infradead.org \ --cc=rodrigo.vivi@intel.com \ --cc=sstabellini@kernel.org \ --cc=tvrtko.ursulin@linux.intel.com \ --cc=willy@infradead.org \ --cc=x86@kernel.org \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.