From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org,
Matt Roper <matthew.d.roper@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Remove dead code from gen8_pte_encode
Date: Fri, 7 Jul 2023 10:17:02 -0400 [thread overview]
Message-ID: <ZKgeGwl0nj9QAptv@intel.com> (raw)
In-Reply-To: <20230707124644.3965281-1-tvrtko.ursulin@linux.intel.com>
On Fri, Jul 07, 2023 at 01:46:44PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Commit 9275277d5324 ("drm/i915: use pat_index instead of cache_level")
> added a dedicated gen12_pte_encode but forgot to remove the Gen12 specific
> bit from gen8_pte_encode.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Fixes: 9275277d5324 ("drm/i915: use pat_index instead of cache_level")
> Cc: Fei Yang <fei.yang@intel.com>
> Cc: Andi Shyti <andi.shyti@linux.intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/gen8_ppgtt.c b/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> index f948d33e5ec5..c8568e5d1147 100644
> --- a/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> +++ b/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> @@ -37,9 +37,6 @@ static u64 gen8_pte_encode(dma_addr_t addr,
> if (unlikely(flags & PTE_READ_ONLY))
> pte &= ~GEN8_PAGE_RW;
>
> - if (flags & PTE_LM)
> - pte |= GEN12_PPGTT_PTE_LM;
> -
> /*
> * For pre-gen12 platforms pat_index is the same as enum
> * i915_cache_level, so the switch-case here is still valid.
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-07-07 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 12:46 [Intel-gfx] [PATCH] drm/i915: Remove dead code from gen8_pte_encode Tvrtko Ursulin
2023-07-07 12:46 ` Tvrtko Ursulin
2023-07-07 14:17 ` Rodrigo Vivi [this message]
2023-07-10 9:25 ` [Intel-gfx] " Tvrtko Ursulin
2023-07-10 9:25 ` Tvrtko Ursulin
2023-07-07 14:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-07-07 17:13 ` [Intel-gfx] [PATCH] " Yang, Fei
2023-07-07 17:13 ` Yang, Fei
2023-07-07 18:03 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2023-07-10 9:35 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-07-10 9:35 ` Andi Shyti
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=ZKgeGwl0nj9QAptv@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=tvrtko.ursulin@linux.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.