dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Oded Gabbay" <ogabbay@kernel.org>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-xe-next-fixes
Date: Tue, 9 Jul 2024 17:31:39 -0400	[thread overview]
Message-ID: <Zo2sO4t32dxqy6Q7@intel.com> (raw)

Hi Dave and Sima,

 Here goes a very early drm-xe-next-fixes with 2 important fixes
 that are going to impact user space.

 1. The first one is the rename of the OA stuff from the bad 'perf'
 name to the xe_observation. Although the rename in the uapi
 header is likely inoffensive because our UMDs always copy the
 header to their code, there's a sysfs filename change that is
 impacting mesa.

 For this one Mesa MR is ready and they are only waiting for this
 pull request to be picked by you so they can merge that to Mesa:
 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30027

 With both sides in place, there won't be any kernel version
 released with the bad naming and no Mesa released using that
 filename. This is the main reason that I'm sending this PR
 earlier than normal.

 2. The second case, which also impact user space is the
 write-back caching mode for system memory on DGFX. In this case
 we introduce a limitation in the cache selection uapi that is
 transparent to UMDs. I mean, no change on their side is needed.
 Coherence is maintained with some know possible visible and
 acceptable/accepted differences in CPU access speed.

 Thanks,
 Rodrigo.

drm-xe-next-fixes-2024-07-09:
UAPI Changes:
- Rename xe perf layer as xe observation layer (Ashutosh)
- Use write-back caching mode for system memory on DGFX (Thomas)

Driver Changes:
- Drop trace_xe_hw_fence_free (Brost)
The following changes since commit 62a05f4ae9c1fb70bc75d494c9c1c373d2c2e374:

  Merge tag 'drm-msm-next-2024-07-04' of https://gitlab.freedesktop.org/drm/msm into drm-next (2024-07-05 12:45:41 +0200)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2024-07-09

for you to fetch changes up to 463108053c19f24fa228863824698d5ca72826b6:

  drm/xe: Drop trace_xe_hw_fence_free (2024-07-09 16:21:26 -0400)

----------------------------------------------------------------
UAPI Changes:
- Rename xe perf layer as xe observation layer (Ashutosh)
- Use write-back caching mode for system memory on DGFX (Thomas)

Driver Changes:
- Drop trace_xe_hw_fence_free (Brost)

----------------------------------------------------------------
Ashutosh Dixit (1):
      drm/xe/uapi: Rename xe perf layer as xe observation layer

Matthew Brost (1):
      drm/xe: Drop trace_xe_hw_fence_free

Thomas Hellström (1):
      drm/xe: Use write-back caching mode for system memory on DGFX

 drivers/gpu/drm/xe/Makefile          |   2 +-
 drivers/gpu/drm/xe/xe_bo.c           |  47 +++++++++------
 drivers/gpu/drm/xe/xe_bo_types.h     |   3 +-
 drivers/gpu/drm/xe/xe_device.c       |   4 +-
 drivers/gpu/drm/xe/xe_device_types.h |   2 +-
 drivers/gpu/drm/xe/xe_gt_types.h     |   2 +-
 drivers/gpu/drm/xe/xe_hw_fence.c     |   1 -
 drivers/gpu/drm/xe/xe_module.c       |   6 +-
 drivers/gpu/drm/xe/xe_oa.c           |  34 +++++------
 drivers/gpu/drm/xe/xe_observation.c  |  93 +++++++++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_observation.h  |  20 +++++++
 drivers/gpu/drm/xe/xe_perf.c         |  92 -----------------------------
 drivers/gpu/drm/xe/xe_perf.h         |  20 -------
 drivers/gpu/drm/xe/xe_trace.h        |   5 --
 include/uapi/drm/xe_drm.h            | 110 +++++++++++++++++++----------------
 15 files changed, 227 insertions(+), 214 deletions(-)
 create mode 100644 drivers/gpu/drm/xe/xe_observation.c
 create mode 100644 drivers/gpu/drm/xe/xe_observation.h
 delete mode 100644 drivers/gpu/drm/xe/xe_perf.c
 delete mode 100644 drivers/gpu/drm/xe/xe_perf.h

             reply	other threads:[~2024-07-09 21:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 21:31 Rodrigo Vivi [this message]
2024-07-10 19:42 ` [PULL] drm-xe-next-fixes Lucas De Marchi
2024-07-10 20:45   ` Rodrigo Vivi
  -- strict thread matches above, loose matches on Subject: below --
2025-08-06 13:24 Rodrigo Vivi
2025-07-31 19:46 Rodrigo Vivi
2025-06-05 19:07 Thomas Hellstrom
2025-05-28 16:21 Thomas Hellstrom
2025-05-23  8:25 Thomas Hellstrom
2025-03-27 15:14 Lucas De Marchi
2025-03-13  4:41 Lucas De Marchi
2024-11-28 15:39 Thomas Hellstrom
2024-11-21 19:39 Thomas Hellstrom
2024-11-15 11:10 Thomas Hellstrom
2024-09-20  2:56 Lucas De Marchi
2024-09-20  3:14 ` Lucas De Marchi
2024-09-12 23:23 Lucas De Marchi
2024-07-18 15:51 Rodrigo Vivi
2024-05-09 16:35 Thomas Hellstrom
2024-05-02 14:26 Thomas Hellstrom
2024-03-15  4:14 Lucas De Marchi
2024-03-04 16:00 Lucas De Marchi
2024-01-16 10:22 Thomas Hellström
2023-12-26 18:27 Rodrigo Vivi

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=Zo2sO4t32dxqy6Q7@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).