Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/5] drm/xe/guc: Add VF_CFG_SCHED_PRIORITY_KEY KLV definition
Date: Mon, 28 Oct 2024 16:34:18 +0100	[thread overview]
Message-ID: <ed410381-ebc8-48b7-afda-431a46ccfab9@intel.com> (raw)
In-Reply-To: <20241023231152.1815-2-michal.wajdeczko@intel.com>

On 10/24/2024 01:11, Michal Wajdeczko wrote:
> This KLV allows to set the scheduling priority for each VF, also
> for the PF.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>   drivers/gpu/drm/xe/abi/guc_klvs_abi.h | 13 +++++++++++++
>   1 file changed, 13 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/abi/guc_klvs_abi.h b/drivers/gpu/drm/xe/abi/guc_klvs_abi.h
> index 37606cf8cc5e..674f1afe38c8 100644
> --- a/drivers/gpu/drm/xe/abi/guc_klvs_abi.h
> +++ b/drivers/gpu/drm/xe/abi/guc_klvs_abi.h
> @@ -291,6 +291,13 @@ enum  {
>    *
>    *      :0: (default)
>    *      :1-65535: number of contexts (Gen12)
> + *
> + * _`GUC_KLV_VF_CFG_SCHED_PRIORITY` : 0x8A0C
> + *      This config controls VF’s scheduling priority.
> + *
> + *      :0: LOW = schedule VF only if it has active work (default)
> + *      :1: NORMAL = schedule VF always, irrespective of whether it has work or not
> + *      :2: HIGH = schedule VF in the next time-slice after current active time-slice completes

Maybe worth to add that VF is scheduled only if it has work?

>    */
>   
>   #define GUC_KLV_VF_CFG_GGTT_START_KEY		0x0001
> @@ -343,6 +350,12 @@ enum  {
>   #define GUC_KLV_VF_CFG_BEGIN_CONTEXT_ID_KEY	0x8a0b
>   #define GUC_KLV_VF_CFG_BEGIN_CONTEXT_ID_LEN	1u
>   
> +#define GUC_KLV_VF_CFG_SCHED_PRIORITY_KEY	0x8a0c
> +#define GUC_KLV_VF_CFG_SCHED_PRIORITY_LEN	1u
> +#define   GUC_SCHED_PRIORITY_LOW		0u
> +#define   GUC_SCHED_PRIORITY_NORMAL		1u
> +#define   GUC_SCHED_PRIORITY_HIGH		2u
> +
>   /*
>    * Workaround keys:
>    */

  reply	other threads:[~2024-10-28 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 23:11 [PATCH 0/5] PF: Add support for VF scheduling priority Michal Wajdeczko
2024-10-23 23:11 ` [PATCH 1/5] drm/xe/guc: Add VF_CFG_SCHED_PRIORITY_KEY KLV definition Michal Wajdeczko
2024-10-28 15:34   ` Laguna, Lukasz [this message]
2024-10-23 23:11 ` [PATCH 2/5] drm/xe/guc: Add VF_CFG_SCHED_PRIORITY to KLV helper Michal Wajdeczko
2024-10-23 23:11 ` [PATCH 3/5] drm/xe/pf: Add functions to configure VF scheduling priority Michal Wajdeczko
2024-10-23 23:11 ` [PATCH 4/5] drm/xe/pf: Allow to control scheduling priority using debugfs Michal Wajdeczko
2024-10-23 23:11 ` [PATCH 5/5] drm/xe/pf: Adjust scheduling priority based on policy change Michal Wajdeczko
2024-10-24 15:30 ` ✓ CI.Patch_applied: success for PF: Add support for VF scheduling priority Patchwork
2024-10-24 15:30 ` ✓ CI.checkpatch: " Patchwork
2024-10-24 15:31 ` ✓ CI.KUnit: " Patchwork
2024-10-24 15:43 ` ✓ CI.Build: " Patchwork
2024-10-24 15:45 ` ✓ CI.Hooks: " Patchwork
2024-10-24 15:46 ` ✓ CI.checksparse: " Patchwork
2024-10-24 16:12 ` ✗ CI.BAT: failure " Patchwork
2024-10-25 18:37 ` ✗ CI.FULL: " Patchwork
2024-10-28 15:51 ` [PATCH 0/5] " Laguna, Lukasz

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=ed410381-ebc8-48b7-afda-431a46ccfab9@intel.com \
    --to=lukasz.laguna@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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