Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	stable@vger.kernel.org, Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v4 1/2] drm/xe: Use non-interruptible wait when moving BO to system
Date: Mon, 16 Dec 2024 10:01:21 +0100	[thread overview]
Message-ID: <24eeb9dcbb1845bdb420df12384f54d60234a411.camel@linux.intel.com> (raw)
In-Reply-To: <20241213122415.3880017-1-nirmoy.das@intel.com>

HI, Nirmoy,

On Fri, 2024-12-13 at 13:24 +0100, Nirmoy Das wrote:
> Ensure a non-interruptible wait is used when moving a bo to
> XE_PL_SYSTEM. This prevents dma_mappings from being removed
> prematurely
> while a GPU job is still in progress, even if the CPU receives a
> signal during the operation.
> 
> Fixes: 75521e8b56e8 ("drm/xe: Perform dma_map when moving system
> buffer objects to TT")
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: <stable@vger.kernel.org> # v6.11+
> Suggested-by: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>

For both patches
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>




> ---
>  drivers/gpu/drm/xe/xe_bo.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index 283cd0294570..06931df876ab 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -733,7 +733,7 @@ static int xe_bo_move(struct ttm_buffer_object
> *ttm_bo, bool evict,
>  	    new_mem->mem_type == XE_PL_SYSTEM) {
>  		long timeout = dma_resv_wait_timeout(ttm_bo-
> >base.resv,
>  						    
> DMA_RESV_USAGE_BOOKKEEP,
> -						     true,
> +						     false,
>  						    
> MAX_SCHEDULE_TIMEOUT);
>  		if (timeout < 0) {
>  			ret = timeout;


      parent reply	other threads:[~2024-12-16  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 12:24 [PATCH v4 1/2] drm/xe: Use non-interruptible wait when moving BO to system Nirmoy Das
2024-12-13 12:24 ` [PATCH v4 2/2] drm/xe: Wait for migration job before unmapping pages Nirmoy Das
2024-12-13 15:02 ` ✓ CI.Patch_applied: success for series starting with [v4,1/2] drm/xe: Use non-interruptible wait when moving BO to system Patchwork
2024-12-13 15:03 ` ✓ CI.checkpatch: " Patchwork
2024-12-13 15:04 ` ✓ CI.KUnit: " Patchwork
2024-12-13 15:22 ` ✓ CI.Build: " Patchwork
2024-12-13 15:24 ` ✓ CI.Hooks: " Patchwork
2024-12-13 15:26 ` ✓ CI.checksparse: " Patchwork
2024-12-13 15:56 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-14  2:46 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-16 15:07   ` Nirmoy Das
2024-12-16  9:01 ` Thomas Hellström [this message]

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=24eeb9dcbb1845bdb420df12384f54d60234a411.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=nirmoy.das@intel.com \
    --cc=stable@vger.kernel.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