All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: matthew.d.roper@intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe : Fix GT looping for standalone media
Date: Tue, 13 Jun 2023 18:58:32 +0000	[thread overview]
Message-ID: <ZIi8WEZD+4Pc3mKK@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20230613094232.3703549-1-riana.tauro@intel.com>

On Tue, Jun 13, 2023 at 03:12:32PM +0530, Riana Tauro wrote:
> Currently the id of primary gt is set using gt_count and not
> the media gt.
> 
> set gt->info.id of media gt using gt_count
> 
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_pci.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index bd1f59b49928..2991cf5365d5 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -590,7 +590,7 @@ static int xe_info_init(struct xe_device *xe,
>  		 * up with platforms that support both together.
>  		 */
>  		drm_WARN_ON(&xe->drm, id != 0);
> -		gt->info.id = 1;

I agree with change but Matt R is the expert here.

If we go with the change the above drm_WARN_ON & FIXME comment need to
be deleted too.

Matt

> +		gt->info.id = xe->info.gt_count++;
>  	}
>  
>  	return 0;
> -- 
> 2.40.0
> 

  parent reply	other threads:[~2023-06-13 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  9:42 [Intel-xe] [PATCH] drm/xe : Fix GT looping for standalone media Riana Tauro
2023-06-13 10:33 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-06-13 10:33 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-06-13 10:34 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-06-13 10:38 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-06-13 10:38 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-06-13 10:39 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-06-13 11:08 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-06-13 18:58 ` Matthew Brost [this message]
2023-06-13 21:39 ` [Intel-xe] [PATCH] " Matt Roper
2023-06-14 17:54   ` Matt Roper
2023-06-15  4:42     ` Riana Tauro

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=ZIi8WEZD+4Pc3mKK@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=riana.tauro@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.