From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/6] VF: Use the runtime registers
Date: Thu, 23 May 2024 21:22:34 +0200 [thread overview]
Message-ID: <20240523192240.844-1-michal.wajdeczko@intel.com> (raw)
Michal Wajdeczko (6):
drm/xe/vf: Use register values obtained from the PF
drm/xe/guc: Add GLOBAL_CFG_GMD_ID KLV definition
drm/xe/vf: Obtain value of GMDID register from GuC
drm/xe/vf: Provide early access to GMDID register
drm/xe/vf: Cache value of the GMDID register
drm/xe/vf: Treat GMDID as another runtime register
drivers/gpu/drm/xe/abi/guc_klvs_abi.h | 14 +++
drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 106 ++++++++++++++++++++++
drivers/gpu/drm/xe/xe_gt_sriov_vf.h | 3 +
drivers/gpu/drm/xe/xe_gt_sriov_vf_types.h | 2 +
drivers/gpu/drm/xe/xe_mmio.c | 4 +
drivers/gpu/drm/xe/xe_pci.c | 47 +++++++++-
6 files changed, 173 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2024-05-23 19:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 19:22 Michal Wajdeczko [this message]
2024-05-23 19:22 ` [PATCH 1/6] drm/xe/vf: Use register values obtained from the PF Michal Wajdeczko
2024-05-23 21:28 ` Matt Roper
2024-05-23 19:22 ` [PATCH 2/6] drm/xe/guc: Add GLOBAL_CFG_GMD_ID KLV definition Michal Wajdeczko
2024-05-23 20:50 ` Matt Roper
2024-05-23 19:22 ` [PATCH 3/6] drm/xe/vf: Obtain value of GMDID register from GuC Michal Wajdeczko
2024-05-23 20:52 ` Matt Roper
2024-05-23 19:22 ` [PATCH 4/6] drm/xe/vf: Provide early access to GMDID register Michal Wajdeczko
2024-05-23 21:08 ` Matt Roper
2024-05-23 21:17 ` Matt Roper
2024-05-23 21:43 ` Michal Wajdeczko
2024-05-23 22:30 ` [PATCH v2 " Michal Wajdeczko
2024-05-23 19:22 ` [PATCH 5/6] drm/xe/vf: Cache value of the " Michal Wajdeczko
2024-05-23 21:20 ` Matt Roper
2024-05-23 19:22 ` [PATCH 6/6] drm/xe/vf: Treat GMDID as another runtime register Michal Wajdeczko
2024-05-23 21:21 ` Matt Roper
2024-05-23 19:29 ` ✓ CI.Patch_applied: success for VF: Use the runtime registers Patchwork
2024-05-23 19:29 ` ✓ CI.checkpatch: " Patchwork
2024-05-23 19:30 ` ✓ CI.KUnit: " Patchwork
2024-05-23 19:41 ` ✓ CI.Build: " Patchwork
2024-05-23 19:44 ` ✓ CI.Hooks: " Patchwork
2024-05-23 19:45 ` ✓ CI.checksparse: " Patchwork
2024-05-23 23:05 ` ✓ CI.Patch_applied: success for VF: Use the runtime registers (rev2) Patchwork
2024-05-23 23:06 ` ✓ CI.checkpatch: " Patchwork
2024-05-23 23:07 ` ✓ CI.KUnit: " Patchwork
2024-05-23 23:18 ` ✓ CI.Build: " Patchwork
2024-05-23 23:19 ` ✗ CI.FULL: failure for VF: Use the runtime registers Patchwork
2024-05-23 23:21 ` ✓ CI.Hooks: success for VF: Use the runtime registers (rev2) Patchwork
2024-05-23 23:22 ` ✓ CI.checksparse: " Patchwork
2024-05-23 23:49 ` ✓ CI.BAT: " Patchwork
2024-05-24 2:10 ` ✗ CI.FULL: failure " Patchwork
2024-05-24 7:50 ` Michal Wajdeczko
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=20240523192240.844-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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