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 0/7] Update GuC ABI definitions
Date: Fri, 29 Mar 2024 17:50:32 +0100	[thread overview]
Message-ID: <92f47e87-a638-44c3-94a8-34f901a92eb5@intel.com> (raw)
In-Reply-To: <xxpank76lzfhakpmqa5srfqzq3fnpxlklttseyczfrajemvjzz@iqxhplnfmpcc>



On 29.03.2024 17:14, Lucas De Marchi wrote:
> On Thu, Mar 28, 2024 at 07:31:40PM +0100, Michal Wajdeczko wrote:
>> In upcoming patches we will use additional messages in communication
>> with the GuC firmware. Add necessary definitions to our ABI header.
> 
> but it would be better if these additions were done when they are
> needed. We don't want to keep updating this with things that may not be
> needed at all (plans always change, ABI may change to fix bugs, etc)

fully understand that, but...

this ABI definitions reflects what current firmware already supports
and it is just complementary to what was already pushed in initial
driver drop without supporting code:
 - [1] GuC VGT Policy KLVs
 - [2] GuC VF Configuration KLVs

[1]
https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/xe/abi/guc_klvs_abi.h#L114

[2]
https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/xe/abi/guc_klvs_abi.h#L154

it will also help me lower my pile of pending patches, so maybe there is
a chance for a small exception ?

Michal

> 
> Lucas De Marchi
> 
>>
>> Michal Wajdeczko (7):
>>  drm/xe/guc: Add PF2GUC_UPDATE_VF_CFG to ABI
>>  drm/xe/guc: Add PF2GUC_UPDATE_VGT_POLICY to ABI
>>  drm/xe/guc: Add GUC2PF_ADVERSE_EVENT to ABI
>>  drm/xe/guc: Add VF2GUC_MATCH_VERSION to ABI
>>  drm/xe/guc: Add VF2GUC_VF_RESET to ABI
>>  drm/xe/guc: Add VF2GUC_QUERY_SINGLE_KLV to ABI
>>  drm/xe/guc: Add GLOBAL_CFG_GMD_ID KLV definition
>>
>> .../gpu/drm/xe/abi/guc_actions_sriov_abi.h    | 289 ++++++++++++++++++
>> drivers/gpu/drm/xe/abi/guc_klvs_abi.h         |  13 +
>> 2 files changed, 302 insertions(+)
>>
>> -- 
>> 2.43.0
>>

  reply	other threads:[~2024-03-29 16:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 18:31 [PATCH 0/7] Update GuC ABI definitions Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 1/7] drm/xe/guc: Add PF2GUC_UPDATE_VF_CFG to ABI Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 2/7] drm/xe/guc: Add PF2GUC_UPDATE_VGT_POLICY " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 3/7] drm/xe/guc: Add GUC2PF_ADVERSE_EVENT " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 4/7] drm/xe/guc: Add VF2GUC_MATCH_VERSION " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 5/7] drm/xe/guc: Add VF2GUC_VF_RESET " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 6/7] drm/xe/guc: Add VF2GUC_QUERY_SINGLE_KLV " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 7/7] drm/xe/guc: Add GLOBAL_CFG_GMD_ID KLV definition Michal Wajdeczko
2024-03-29  2:58 ` ✓ CI.Patch_applied: success for Update GuC ABI definitions Patchwork
2024-03-29  2:59 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-29  3:00 ` ✓ CI.KUnit: success " Patchwork
2024-03-29  3:11 ` ✓ CI.Build: " Patchwork
2024-03-29  3:13 ` ✓ CI.Hooks: " Patchwork
2024-03-29  3:15 ` ✓ CI.checksparse: " Patchwork
2024-03-29  3:50 ` ✓ CI.BAT: " Patchwork
2024-03-29 16:14 ` [PATCH 0/7] " Lucas De Marchi
2024-03-29 16:50   ` Michal Wajdeczko [this message]
2024-04-01 12:54     ` Lucas De Marchi
2024-04-04  1:10       ` John Harrison

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=92f47e87-a638-44c3-94a8-34f901a92eb5@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