All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v4 1/4] drm/xe: Remove safety check from __xe_ttm_stolen_io_mem_reserve_stolen
Date: Thu, 9 May 2024 21:41:53 -0400	[thread overview]
Message-ID: <Zj17YXyU3L0pV3qY@intel.com> (raw)
In-Reply-To: <20240506103604.146146-2-maarten.lankhorst@linux.intel.com>

On Mon, May 06, 2024 at 12:36:01PM +0200, Maarten Lankhorst wrote:
> This is invalid with display code when reworking DPT pinning.
> The only reason we added it, was because originally all display
> allocations also had the bit set.
> 
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c b/drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c
> index f77367329760..1613290b9eda 100644
> --- a/drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c
> +++ b/drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c
> @@ -298,10 +298,6 @@ static int __xe_ttm_stolen_io_mem_reserve_stolen(struct xe_device *xe,
>  
>  	XE_WARN_ON(IS_DGFX(xe));
>  
> -	/* XXX: Require BO to be mapped to GGTT? */
> -	if (drm_WARN_ON(&xe->drm, !(bo->flags & XE_BO_FLAG_GGTT)))
> -		return -EIO;
> -
>  	/* GGTT is always contiguously mapped */
>  	mem->bus.offset = xe_bo_ggtt_addr(bo) + mgr->io_base;
>  
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-05-10  1:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 10:36 [PATCH v4 0/4] drm/xe: More fb pinning optimizations Maarten Lankhorst
2024-05-06 10:36 ` [PATCH v4 1/4] drm/xe: Remove safety check from __xe_ttm_stolen_io_mem_reserve_stolen Maarten Lankhorst
2024-05-10  1:41   ` Rodrigo Vivi [this message]
2024-05-06 10:36 ` [PATCH v4 2/4] drm/xe/display: Preparations for preallocating dpt bo Maarten Lankhorst
2024-05-10  1:45   ` Rodrigo Vivi
2024-05-06 10:36 ` [PATCH v4 3/4] drm/xe: Use simple xchg to cache DPT Maarten Lankhorst
2024-05-06 10:36 ` [PATCH v4 4/4] drm/xe/display: Re-use display vmas when possible Maarten Lankhorst
2024-05-06 11:14 ` ✓ CI.Patch_applied: success for drm/xe: More fb pinning optimizations Patchwork
2024-05-06 11:14 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-06 11:15 ` ✓ CI.KUnit: success " Patchwork
2024-05-06 11:28 ` ✓ CI.Build: " Patchwork
2024-05-06 11:31 ` ✓ CI.Hooks: " Patchwork
2024-05-06 11:32 ` ✗ CI.checksparse: warning " Patchwork
2024-05-06 11:41 ` ✗ Fi.CI.CHECKPATCH: " Patchwork
2024-05-06 11:47 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-06 12:11 ` ✓ CI.BAT: " Patchwork
2024-05-06 13:22 ` ✗ CI.FULL: failure " Patchwork
2024-05-06 16:16 ` ✓ Fi.CI.IGT: success " 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=Zj17YXyU3L0pV3qY@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@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.