Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH v2 0/5] Add SR-IOV GuC Relay PF services
Date: Tue, 23 Apr 2024 20:04:31 +0200	[thread overview]
Message-ID: <20240423180436.2089-1-michal.wajdeczko@intel.com> (raw)

v2: describe purpose of the MAJOR|MINOR_ANY (Piotr)
    update description on QUERY_RUNTIME action (Piotr)
    start using helper (Piotr)
    make gt param const to allow use in xe_mmio_in_range()
    assert that we adjust both or none addr in xe_mmio_read64_2x32()
    fix params indent and improve struct description (Piotr)
    fix kernel-doc annotation (CI.hooks)
    use VF2PF_QUERY_RUNTIME_NO_LIMIT

Michal Wajdeczko (5):
  drm/xe/guc: Add GuC Relay ABI version 1.0 definitions
  drm/xe: Add helper to calculate adjusted register offset
  drm/xe: Add few more GT register definitions
  drm/xe/pf: Add SR-IOV GuC Relay PF services
  drm/xe/kunit: Add PF service tests

 drivers/gpu/drm/xe/Makefile                   |   1 +
 .../gpu/drm/xe/abi/guc_relay_actions_abi.h    | 170 +++++-
 drivers/gpu/drm/xe/regs/xe_gt_regs.h          |   3 +
 .../xe/tests/xe_gt_sriov_pf_service_test.c    | 232 ++++++++
 drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c   | 550 ++++++++++++++++++
 drivers/gpu/drm/xe/xe_gt_sriov_pf_service.h   |  36 ++
 .../gpu/drm/xe/xe_gt_sriov_pf_service_types.h |  52 ++
 drivers/gpu/drm/xe/xe_gt_sriov_pf_types.h     |   5 +
 drivers/gpu/drm/xe/xe_guc_relay.c             |   8 +-
 drivers/gpu/drm/xe/xe_mmio.c                  |  38 +-
 drivers/gpu/drm/xe/xe_mmio.h                  |   7 +
 11 files changed, 1076 insertions(+), 26 deletions(-)
 create mode 100644 drivers/gpu/drm/xe/tests/xe_gt_sriov_pf_service_test.c
 create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
 create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_service.h
 create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_service_types.h

-- 
2.43.0


             reply	other threads:[~2024-04-23 18:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 18:04 Michal Wajdeczko [this message]
2024-04-23 18:04 ` [PATCH v2 1/5] drm/xe/guc: Add GuC Relay ABI version 1.0 definitions Michal Wajdeczko
2024-04-23 18:04 ` [PATCH v2 2/5] drm/xe: Add helper to calculate adjusted register offset Michal Wajdeczko
2024-04-23 19:19   ` Piotr Piórkowski
2024-04-23 18:04 ` [PATCH v2 3/5] drm/xe: Add few more GT register definitions Michal Wajdeczko
2024-04-23 18:04 ` [PATCH v2 4/5] drm/xe/pf: Add SR-IOV GuC Relay PF services Michal Wajdeczko
2024-04-23 18:04 ` [PATCH v2 5/5] drm/xe/kunit: Add PF service tests Michal Wajdeczko
2024-04-23 21:06 ` ✓ CI.Patch_applied: success for Add SR-IOV GuC Relay PF services (rev3) Patchwork
2024-04-23 21:06 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-23 21:07 ` ✓ CI.KUnit: success " Patchwork
2024-04-23 21:19 ` ✓ CI.Build: " Patchwork
2024-04-23 21:22 ` ✓ CI.Hooks: " Patchwork
2024-04-23 21:23 ` ✓ CI.checksparse: " Patchwork
2024-04-23 22:02 ` ✓ CI.BAT: " Patchwork
2024-04-24 10:57 ` ✗ CI.FULL: failure " Patchwork
2024-04-24 11:24   ` Michal Wajdeczko
2024-04-26  7:21     ` Balne, VinayX Kumar Goud

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=20240423180436.2089-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