From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/mtl: Apply notify_guc to all GTs
Date: Tue, 31 Oct 2023 11:57:08 +0100 [thread overview]
Message-ID: <60cab0e2-8b6f-0ec9-e6b0-a359f157757a@linux.intel.com> (raw)
In-Reply-To: <d18c18c2-bd0b-42b6-a7a8-034f1afc4a80@intel.com>
merged to drm-next
Thanks,
Nirmoy
On 10/25/2023 3:12 PM, Andrzej Hajda wrote:
>
>
> On 25.10.2023 12:28, Nirmoy Das wrote:
>> Handle platforms with multiple GTs by iterate over all GTs.
>> Add a Fixes commit so this gets propagated for MTL support.
>>
>> Fixes: 213c43676beb ("drm/i915/mtl: Remove the 'force_probe'
>> requirement for Meteor Lake")
>> Suggested-by: John Harrison <john.c.harrison@intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_debugfs_params.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_debugfs_params.c
>> b/drivers/gpu/drm/i915/i915_debugfs_params.c
>> index 614bde321589..8bca02025e09 100644
>> --- a/drivers/gpu/drm/i915/i915_debugfs_params.c
>> +++ b/drivers/gpu/drm/i915/i915_debugfs_params.c
>> @@ -38,10 +38,13 @@ static int i915_param_int_open(struct inode
>> *inode, struct file *file)
>> static int notify_guc(struct drm_i915_private *i915)
>> {
>> - int ret = 0;
>> + struct intel_gt *gt;
>> + int i, ret = 0;
>> - if (intel_uc_uses_guc_submission(&to_gt(i915)->uc))
>> - ret = intel_guc_global_policies_update(&to_gt(i915)->uc.guc);
>> + for_each_gt(gt, i915, i) {
>> + if (intel_uc_uses_guc_submission(>->uc))
>> + ret = intel_guc_global_policies_update(>->uc.guc);
>> + }
>
> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
>
> Regards
> Andrzej
>
>> return ret;
>> }
>
next prev parent reply other threads:[~2023-10-31 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 10:28 [Intel-gfx] [PATCH] drm/i915/mtl: Apply notify_guc to all GTs Nirmoy Das
2023-10-25 10:31 ` Andi Shyti
2023-10-25 13:12 ` Andrzej Hajda
2023-10-31 10:57 ` Nirmoy Das [this message]
2023-10-31 10:59 ` Nirmoy Das
2023-10-25 19:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-10-26 19:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/mtl: Apply notify_guc to all GTs (rev2) Patchwork
2023-10-27 19:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/mtl: Apply notify_guc to all GTs (rev3) Patchwork
2023-10-30 3:43 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-06 12:45 ` [Intel-gfx] [PATCH] drm/i915/mtl: Apply notify_guc to all GTs Jani Nikula
2023-11-06 12:51 ` Nirmoy Das
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=60cab0e2-8b6f-0ec9-e6b0-a359f157757a@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@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.