public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v6 5/5] drm/xe: Remove xe_ggtt_node_allocated
Date: Mon, 26 Jan 2026 22:13:44 +0100	[thread overview]
Message-ID: <7bb86c2a-6f13-49ef-995b-a1a657316b19@intel.com> (raw)
In-Reply-To: <20260126104604.988024-6-dev@lankhorst.se>



On 1/26/2026 11:46 AM, Maarten Lankhorst wrote:
> With the intermediate state gone, no longer useful. Just check against
> NULL where needed.
> 
> Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>
> ---
>  drivers/gpu/drm/xe/display/xe_fb_pin.c     |  3 +--
>  drivers/gpu/drm/xe/xe_ggtt.c               | 17 -----------------
>  drivers/gpu/drm/xe/xe_ggtt.h               |  1 -
>  drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 12 ++++++------
>  4 files changed, 7 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/display/xe_fb_pin.c b/drivers/gpu/drm/xe/display/xe_fb_pin.c
> index 5ff583699325c..e1d29b6ba043e 100644
> --- a/drivers/gpu/drm/xe/display/xe_fb_pin.c
> +++ b/drivers/gpu/drm/xe/display/xe_fb_pin.c
> @@ -352,8 +352,7 @@ static void __xe_unpin_fb_vma(struct i915_vma *vma)
>  
>  	if (vma->dpt)
>  		xe_bo_unpin_map_no_vm(vma->dpt);
> -	else if (!xe_ggtt_node_allocated(vma->bo->ggtt_node[tile_id]) ||
> -		 vma->bo->ggtt_node[tile_id] != vma->node)
> +	else if (vma->bo->ggtt_node[tile_id] != vma->node)

this isn't 1:1 to what the commit message says, can you explain why?

>  		xe_ggtt_node_remove(vma->node, false);
>  
>  	ttm_bo_reserve(&vma->bo->ttm, false, false, NULL);

  reply	other threads:[~2026-01-26 21:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 10:45 [PATCH v6 0/5] drm/xe: Privatize struct xe_ggtt Maarten Lankhorst
2026-01-26 10:46 ` [PATCH v6 1/5] drm/xe: Make xe_ggtt_node offset relative to starting offset Maarten Lankhorst
2026-01-26 21:01   ` Michal Wajdeczko
2026-01-26 10:46 ` [PATCH v6 2/5] drm/xe: Rewrite GGTT VF initialization Maarten Lankhorst
2026-01-26 21:02   ` Michal Wajdeczko
2026-01-26 10:46 ` [PATCH v6 3/5] drm/xe: Move struct xe_ggtt to xe_ggtt.c Maarten Lankhorst
2026-01-26 21:06   ` Michal Wajdeczko
2026-01-26 10:46 ` [PATCH v6 4/5] drm/xe: Make xe_ggtt_node_insert return a node Maarten Lankhorst
2026-01-26 21:07   ` Michal Wajdeczko
2026-01-26 10:46 ` [PATCH v6 5/5] drm/xe: Remove xe_ggtt_node_allocated Maarten Lankhorst
2026-01-26 21:13   ` Michal Wajdeczko [this message]
2026-01-26 14:26 ` ✓ i915.CI.BAT: success for drm/xe: Privatize struct xe_ggtt Patchwork
2026-01-26 18:16 ` ✗ i915.CI.Full: 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=7bb86c2a-6f13-49ef-995b-a1a657316b19@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=dev@lankhorst.se \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.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: 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