Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 05/14] drm/xe/pf: Add functions to bulk configure EQ/PT on GT
Date: Mon, 27 Oct 2025 21:12:37 +0100	[thread overview]
Message-ID: <e9d5224e-b694-44d4-ab88-b8287a088da7@intel.com> (raw)
In-Reply-To: <i5dgkgqu5paensngw45gstdxgdpjaqukuoi3ygioimw4vyia74@vj3vegarb4qb>



On 10/27/2025 8:03 PM, Lucas De Marchi wrote:
> On Mon, Oct 20, 2025 at 08:24:05PM +0200, Michal Wajdeczko wrote:
>> We already have functions to bulk configure 'hard' resources like
>> GGTT, LMEM or GuC context/doorbells IDs. Now add functions for the
>> 'soft' scheduling parameters, as we will need them soon in the
>> upcoming patches.
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 56 ++++++++++++++++++++++
>> drivers/gpu/drm/xe/xe_gt_sriov_pf_config.h |  2 +
>> 2 files changed, 58 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
>> index 0a591b86d94e..99d5fb68174c 100644
>> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
>> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
>> @@ -1778,6 +1778,34 @@ u32 xe_gt_sriov_pf_config_get_exec_quantum(struct xe_gt *gt, unsigned int vfid)
>>     return exec_quantum;
>> }
>>
>> +/**
>> + * xe_gt_sriov_pf_config_bulk_set_exec_quantum() - Configure execution quantum for PF and VFs.
>> + * @gt: the &xe_gt to configure
>> + * @exec_quantum: requested execution quantum in milliseconds (0 is infinity)
>> + *
>> + * This function can only be called on PF.
>> + *
>> + * Return: 0 on success or a negative error code on failure.
>> + */
>> +int xe_gt_sriov_pf_config_bulk_set_exec_quantum(struct xe_gt *gt, u32 exec_quantum)
>> +{
>> +    unsigned int totalvfs = xe_gt_sriov_pf_get_totalvfs(gt);
>> +    unsigned int n;
>> +    int err = 0;
>> +
>> +    mutex_lock(xe_gt_sriov_pf_master_mutex(gt));
>> +    for (n = 0; n <= totalvfs; n++) {
>> +        err = pf_provision_exec_quantum(gt, VFID(n), exec_quantum);
> 
> Given now the function accepts PFID, it's weird to pass VFID(n).

PFID is still VFID(0)

> Any advantage on using that nop macro?

the function pf_provision_exec_quantum() expects "vfid" anyway
so use of the macro was supposed to be self-documenting that
we are not passing any random integer here

but I can drop this macro here if you want

> 
> 
> Lucas De Marchi


  reply	other threads:[~2025-10-27 20:13 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 18:24 [PATCH 00/14] PF: Add sriov_admin sysfs tree Michal Wajdeczko
2025-10-20 18:24 ` [PATCH 01/14] drm/xe/pf: Prepare sysfs for SR-IOV admin attributes Michal Wajdeczko
2025-10-24 19:43   ` Rodrigo Vivi
2025-10-27 17:11   ` Lucas De Marchi
2025-10-27 17:59     ` Michal Wajdeczko
2025-10-27 18:30       ` Lucas De Marchi
2025-10-20 18:24 ` [PATCH 02/14] drm/xe/pf: Take RPM during calls to SR-IOV attr.store() Michal Wajdeczko
2025-10-27 17:14   ` Lucas De Marchi
2025-10-20 18:24 ` [PATCH 03/14] drm/xe/pf: Allow change PF and VFs EQ/PT using sysfs Michal Wajdeczko
2025-10-24 19:45   ` Rodrigo Vivi
2025-10-27 17:27   ` Lucas De Marchi
2025-10-27 18:09     ` Michal Wajdeczko
2025-10-27 18:32       ` Lucas De Marchi
2025-10-20 18:24 ` [PATCH 04/14] drm/xe/pf: Relax report helper to accept PF in bulk configs Michal Wajdeczko
2025-10-27 18:50   ` Lucas De Marchi
2025-10-20 18:24 ` [PATCH 05/14] drm/xe/pf: Add functions to bulk configure EQ/PT on GT Michal Wajdeczko
2025-10-27 19:03   ` Lucas De Marchi
2025-10-27 20:12     ` Michal Wajdeczko [this message]
2025-10-20 18:24 ` [PATCH 06/14] drm/xe/pf: Add functions to bulk provision EQ/PT Michal Wajdeczko
2025-10-27 19:18   ` Lucas De Marchi
2025-10-20 18:24 ` [PATCH 07/14] drm/xe/pf: Allow bulk change all VFs EQ/PT using sysfs Michal Wajdeczko
2025-10-24 19:46   ` Rodrigo Vivi
2025-10-27 19:28   ` Lucas De Marchi
2025-10-27 20:15     ` Michal Wajdeczko
2025-10-20 18:24 ` [PATCH 08/14] drm/xe/pf: Add functions to provision scheduling priority Michal Wajdeczko
2025-10-28 11:17   ` Piotr Piórkowski
2025-10-20 18:24 ` [PATCH 09/14] drm/xe/pf: Allow bulk change all VFs priority using sysfs Michal Wajdeczko
2025-10-24 19:47   ` Rodrigo Vivi
2025-10-20 18:24 ` [PATCH 10/14] drm/xe/pf: Allow change PF scheduling " Michal Wajdeczko
2025-10-24 19:47   ` Rodrigo Vivi
2025-10-20 18:24 ` [PATCH 11/14] drm/xe/pf: Promote xe_pci_sriov_get_vf_pdev Michal Wajdeczko
2025-10-28  9:57   ` Piotr Piórkowski
2025-10-28 12:22     ` Michal Wajdeczko
2025-10-28 16:03       ` Piotr Piórkowski
2025-10-20 18:24 ` [PATCH 12/14] drm/xe/pf: Add sysfs device symlinks to enabled VFs Michal Wajdeczko
2025-10-24 19:47   ` Rodrigo Vivi
2025-10-20 18:24 ` [PATCH 13/14] drm/xe/pf: Allow to stop and reset VF using sysfs Michal Wajdeczko
2025-10-24 19:51   ` Rodrigo Vivi
2025-10-27 20:58     ` Lucas De Marchi
2025-10-20 18:24 ` [PATCH 14/14] drm/xe/pf: Add documentation for sriov_admin attributes Michal Wajdeczko
2025-10-27 16:44   ` Rodrigo Vivi
2025-10-21  4:35 ` ✗ CI.checkpatch: warning for PF: Add sriov_admin sysfs tree Patchwork
2025-10-21  4:36 ` ✓ CI.KUnit: success " Patchwork
2025-10-21 10:19 ` ✗ Xe.CI.Full: failure " 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=e9d5224e-b694-44d4-ab88-b8287a088da7@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox