From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v6 3/8] drm/i915/gtt: drop unneeded make_unshrinkable
Date: Wed, 6 Oct 2021 10:02:39 +0200 [thread overview]
Message-ID: <2310ad7d-7edf-c012-389e-4201072c65ee@linux.intel.com> (raw)
In-Reply-To: <20211005182405.915100-3-matthew.auld@intel.com>
On 10/5/21 20:24, Matthew Auld wrote:
> We already do this when mapping the pages.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/gen6_ppgtt.c | 1 -
> drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 1 -
> 2 files changed, 2 deletions(-)
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
> diff --git a/drivers/gpu/drm/i915/gt/gen6_ppgtt.c b/drivers/gpu/drm/i915/gt/gen6_ppgtt.c
> index 890191f286e3..baea9770200a 100644
> --- a/drivers/gpu/drm/i915/gt/gen6_ppgtt.c
> +++ b/drivers/gpu/drm/i915/gt/gen6_ppgtt.c
> @@ -185,7 +185,6 @@ static void gen6_alloc_va_range(struct i915_address_space *vm,
>
> pt = stash->pt[0];
> __i915_gem_object_pin_pages(pt->base);
> - i915_gem_object_make_unshrinkable(pt->base);
>
> fill32_px(pt, vm->scratch[0]->encode);
>
> diff --git a/drivers/gpu/drm/i915/gt/gen8_ppgtt.c b/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> index 037a9a6e4889..8af2f709571c 100644
> --- a/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> +++ b/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> @@ -301,7 +301,6 @@ static void __gen8_ppgtt_alloc(struct i915_address_space * const vm,
>
> pt = stash->pt[!!lvl];
> __i915_gem_object_pin_pages(pt->base);
> - i915_gem_object_make_unshrinkable(pt->base);
>
> fill_px(pt, vm->scratch[lvl]->encode);
>
next prev parent reply other threads:[~2021-10-06 8:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 18:23 [Intel-gfx] [PATCH v6 1/8] drm/i915/gem: Break out some shmem backend utils Matthew Auld
2021-10-05 18:23 ` [Intel-gfx] [PATCH v6 2/8] drm/i915/ttm: add tt shmem backend Matthew Auld
2021-10-05 18:24 ` [Intel-gfx] [PATCH v6 3/8] drm/i915/gtt: drop unneeded make_unshrinkable Matthew Auld
2021-10-06 8:02 ` Thomas Hellström [this message]
2021-10-05 18:24 ` [Intel-gfx] [PATCH v6 4/8] drm/i915: drop unneeded make_unshrinkable in free_object Matthew Auld
2021-10-06 8:03 ` Thomas Hellström
2021-10-05 18:24 ` [Intel-gfx] [PATCH v6 5/8] drm/i915: add some kernel-doc for shrink_pin and friends Matthew Auld
2021-10-06 8:03 ` Thomas Hellström
2021-10-05 18:24 ` [Intel-gfx] [PATCH v6 6/8] drm/i915/ttm: move shrinker management into adjust_lru Matthew Auld
2021-10-06 8:10 ` Thomas Hellström
2021-10-05 18:24 ` [Intel-gfx] [PATCH v6 7/8] drm/i915/ttm: use cached system pages when evicting lmem Matthew Auld
2021-10-05 18:24 ` [Intel-gfx] [PATCH v6 8/8] drm/i915/ttm: enable shmem tt backend Matthew Auld
2021-10-05 23:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v6,1/8] drm/i915/gem: Break out some shmem backend utils Patchwork
2021-10-05 23:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-10-06 0:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-06 5:17 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=2310ad7d-7edf-c012-389e-4201072c65ee@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox