Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>,
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Don't show client busyness in fdinfo with GuC submission
Date: Thu, 14 Apr 2022 11:05:10 -0700	[thread overview]
Message-ID: <2c834128-08bd-04cc-96ca-2f37f24eccbe@intel.com> (raw)
In-Reply-To: <20220413225732.34943-1-ashutosh.dixit@intel.com>



On 4/13/2022 3:57 PM, Ashutosh Dixit wrote:
> Client busyness is not available when GuC submission is used. Don't show it
> in fdinfo till this is supported by GuC.

GuC does support this, but we don't yet have code in place in i915 to 
fetch the data, so this commit message needs a slightly rewording to 
make that clear.

>
> Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/5564
> Fixes: 055634e4b62f ("drm/i915: Expose client engine utilisation via fdinfo")
> Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> Cc: John Harrison <john.c.harrison@intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
>   drivers/gpu/drm/i915/i915_drm_client.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drm_client.c b/drivers/gpu/drm/i915/i915_drm_client.c
> index e539f6b23060..e7fae4a326ab 100644
> --- a/drivers/gpu/drm/i915/i915_drm_client.c
> +++ b/drivers/gpu/drm/i915/i915_drm_client.c
> @@ -145,7 +145,7 @@ void i915_drm_client_fdinfo(struct seq_file *m, struct file *f)
>   		   PCI_SLOT(pdev->devfn), PCI_FUNC(pdev->devfn));
>   	seq_printf(m, "drm-client-id:\t%u\n", client->id);
>   
> -	if (GRAPHICS_VER(i915) < 8)
> +	if (GRAPHICS_VER(i915) < 8 || intel_guc_submission_is_used(&i915->gt0.uc.guc))

 From outside the GuC code we usually call intel_uc_uses_guc_submission().
Also, this needs a comment to explain that this is temporary and will be 
removed once we implement the feature in the GuC submission back-end.

Daniele

>   		return;
>   
>   	for (i = 0; i < ARRAY_SIZE(uabi_class_names); i++)


  parent reply	other threads:[~2022-04-14 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 22:57 [Intel-gfx] [PATCH] drm/i915: Don't show client busyness in fdinfo with GuC submission Ashutosh Dixit
2022-04-14  4:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-04-14 18:05 ` Ceraolo Spurio, Daniele [this message]
2022-04-14 18:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Don't show client busyness in fdinfo with GuC submission (rev2) Patchwork
2022-04-14 21:24 ` [Intel-gfx] [PATCH v2] drm/i915: Don't show engine information in fdinfo with GuC submission Ashutosh Dixit
2022-04-15  0:14   ` Ceraolo Spurio, Daniele
2022-04-14 22:31 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Don't show client busyness in fdinfo with GuC submission (rev2) Patchwork
2022-04-14 23:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Don't show client busyness in fdinfo with GuC submission (rev3) Patchwork
2022-04-15  0:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-15  0:25 ` [Intel-gfx] [PATCH v3] drm/i915: Don't show engine information in fdinfo with GuC submission Ashutosh Dixit
2022-04-27  9:15   ` Tvrtko Ursulin
2022-04-27 15:43     ` Dixit, Ashutosh
2022-04-27 17:16       ` Tvrtko Ursulin
2022-04-27 18:24         ` Dixit, Ashutosh
2022-04-15  2:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Don't show client busyness in fdinfo with GuC submission (rev4) Patchwork
2022-04-15  2:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-15  8:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=2c834128-08bd-04cc-96ca-2f37f24eccbe@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-gfx@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