From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 0/5] PF: Add support for VF scheduling priority
Date: Mon, 28 Oct 2024 16:51:42 +0100 [thread overview]
Message-ID: <c2e7ea27-3c71-43cb-bae1-4edeeec3eb8f@intel.com> (raw)
In-Reply-To: <20241023231152.1815-1-michal.wajdeczko@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On 10/24/2024 01:11, Michal Wajdeczko wrote:
> Michal Wajdeczko (5):
> drm/xe/guc: Add VF_CFG_SCHED_PRIORITY_KEY KLV definition
> drm/xe/guc: Add VF_CFG_SCHED_PRIORITY to KLV helper
> drm/xe/pf: Add functions to configure VF scheduling priority
> drm/xe/pf: Allow to control scheduling priority using debugfs
> drm/xe/pf: Adjust scheduling priority based on policy change
>
> drivers/gpu/drm/xe/abi/guc_klvs_abi.h | 13 ++++
> drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 76 +++++++++++++++++++
> drivers/gpu/drm/xe/xe_gt_sriov_pf_config.h | 3 +
> .../gpu/drm/xe/xe_gt_sriov_pf_config_types.h | 2 +
> drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c | 5 ++
> drivers/gpu/drm/xe/xe_gt_sriov_pf_policy.c | 25 +++++-
> drivers/gpu/drm/xe/xe_guc_klv_helpers.c | 2 +
> 7 files changed, 123 insertions(+), 3 deletions(-)
One nit in KLV documentation, but overall all looks good. For the series:
Reviewed-by: Lukasz Laguna <lukasz.laguna@intel.com
<mailto:lukasz.laguna@intel.com>>
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
prev parent reply other threads:[~2024-10-28 15:51 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
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 ` Laguna, Lukasz [this message]
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=c2e7ea27-3c71-43cb-bae1-4edeeec3eb8f@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