Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [RFC 0/5] Some uapi alignment in response to the uapi review
Date: Fri, 8 Sep 2023 16:32:57 -0400	[thread overview]
Message-ID: <20230908203302.449041-1-rodrigo.vivi@intel.com> (raw)

MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Link: https://lore.kernel.org/all/863bebd0c624d6fc2b38c0a06b63e468b4185128.camel@linux.intel.com

The most intrusive in this series is the s/gts/gt_list. I could live with gts,
but it looks like gt_list is preferred one.

Another one that I'm looking for inputs is in the consolidation of the gt_id
as the unique number withing the PCI device, i.e., regarless of the tile.

so we might have
tile0/gt0
tile0/gt1
tile1/gt2
tile1/gt3

instead of the other option
which would be the gt_id per tile:
tile0/gt0
tile0/gt1
tile1/gt0
tile1/gt1

After this consolidation I'm planning to go and even remove the tile<n>
from the sysfs and tile would become an information file inside the gt directory.

Thoughts?

Thanks,
Rodrigo.

Rodrigo Vivi (5):
  drm/xe: Kill XE_VM_PROPERTY_BIND_OP_ERROR_CAPTURE_ADDRESS extension
  drm/xe/uapi: Document drm_xe_query_gt.
  drm/xe/uapi: Replace useless 'instance' per unique gt_id.
  drm/xe/uapi: Remove unused field of drm_xe_query_gt
  drm/xe/uapi: Rename gts to gt_list.

 drivers/gpu/drm/xe/xe_gt_types.h |   2 +-
 drivers/gpu/drm/xe/xe_pci.c      |   4 -
 drivers/gpu/drm/xe/xe_query.c    |  40 +++++-----
 drivers/gpu/drm/xe/xe_vm.c       | 129 +------------------------------
 include/uapi/drm/xe_drm.h        | 116 ++++++++++++---------------
 5 files changed, 72 insertions(+), 219 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-09-08 20:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 20:32 Rodrigo Vivi [this message]
2023-09-08 20:32 ` [Intel-xe] [RFC 1/5] drm/xe: Kill XE_VM_PROPERTY_BIND_OP_ERROR_CAPTURE_ADDRESS extension Rodrigo Vivi
2023-09-13 18:42   ` Matthew Brost
2023-09-08 20:32 ` [Intel-xe] [RFC 2/5] drm/xe/uapi: Document drm_xe_query_gt Rodrigo Vivi
2023-09-13 19:55   ` Matt Roper
2023-09-13 21:12     ` Rodrigo Vivi
2023-09-13 21:46       ` Matt Roper
2023-09-13 21:55         ` Rodrigo Vivi
2023-09-14 13:57           ` Souza, Jose
2023-09-14 14:07             ` Rodrigo Vivi
2023-09-08 20:33 ` [Intel-xe] [RFC 3/5] drm/xe/uapi: Replace useless 'instance' per unique gt_id Rodrigo Vivi
2023-09-08 20:33 ` [Intel-xe] [RFC 4/5] drm/xe/uapi: Remove unused field of drm_xe_query_gt Rodrigo Vivi
2023-09-08 20:33 ` [Intel-xe] [RFC 5/5] drm/xe/uapi: Rename gts to gt_list Rodrigo Vivi
2023-09-08 20:43   ` Matt Roper
2023-09-08 20:36 ` [Intel-xe] ✓ CI.Patch_applied: success for Some uapi alignment in response to the uapi review Patchwork
2023-09-08 20:36 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-08 20:37 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-08 20:44 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-08 20:45 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-08 20:46 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-08 21:19 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork

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=20230908203302.449041-1-rodrigo.vivi@intel.com \
    --to=rodrigo.vivi@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