From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Peter Zijlstra <peterz@infradead.org>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-mm@kvack.org
Subject: add remap_pfn_range_notrack instead of reinventing it in i915
Date: Mon, 1 Mar 2021 09:33:18 +0100 [thread overview]
Message-ID: <20210301083320.943079-1-hch@lst.de> (raw)
Hi all,
i915 has some reason to want to avoid the track_pfn_remap overhead in
remap_pfn_range. Add a function to the core VM to do just that rather
than reinventing the functionality poorly in the driver.
Note that the remap_io_sg path does get exercises when using Xorg on my
Thinkpad X1, so this should be considered lightly tested, I've not
managed to hit the remap_io_mapping path at all.
Diffstat:
drivers/gpu/drm/i915/i915_mm.c | 101 ++++++++++-------------------------------
include/linux/mm.h | 2
mm/memory.c | 52 ++++++++++++---------
3 files changed, 60 insertions(+), 95 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
linux-mm@kvack.org
Subject: [Intel-gfx] add remap_pfn_range_notrack instead of reinventing it in i915
Date: Mon, 1 Mar 2021 09:33:18 +0100 [thread overview]
Message-ID: <20210301083320.943079-1-hch@lst.de> (raw)
Hi all,
i915 has some reason to want to avoid the track_pfn_remap overhead in
remap_pfn_range. Add a function to the core VM to do just that rather
than reinventing the functionality poorly in the driver.
Note that the remap_io_sg path does get exercises when using Xorg on my
Thinkpad X1, so this should be considered lightly tested, I've not
managed to hit the remap_io_mapping path at all.
Diffstat:
drivers/gpu/drm/i915/i915_mm.c | 101 ++++++++++-------------------------------
include/linux/mm.h | 2
mm/memory.c | 52 ++++++++++++---------
3 files changed, 60 insertions(+), 95 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-03-01 8:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:33 Christoph Hellwig [this message]
2021-03-01 8:33 ` [Intel-gfx] add remap_pfn_range_notrack instead of reinventing it in i915 Christoph Hellwig
2021-03-01 8:33 ` [PATCH 1/2] mm: add remap_pfn_range_notrack Christoph Hellwig
2021-03-01 8:33 ` [Intel-gfx] " Christoph Hellwig
2021-03-01 8:33 ` [PATCH 2/2] i915: use remap_pfn_range_notrack Christoph Hellwig
2021-03-01 8:33 ` [Intel-gfx] " Christoph Hellwig
2021-03-01 8:44 ` add remap_pfn_range_notrack instead of reinventing it in i915 Daniel Vetter
2021-03-01 8:44 ` [Intel-gfx] " Daniel Vetter
2021-03-01 8:44 ` Daniel Vetter
2021-03-01 8:45 ` Christoph Hellwig
2021-03-01 8:45 ` [Intel-gfx] " Christoph Hellwig
2021-03-01 9:13 ` Daniel Vetter
2021-03-01 9:13 ` Daniel Vetter
2021-03-01 9:13 ` Daniel Vetter
2021-03-01 8:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] mm: add remap_pfn_range_notrack Patchwork
2021-03-01 8:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-03-01 9:24 ` [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=20210301083320.943079-1-hch@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=rodrigo.vivi@intel.com \
/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: link
Be 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.