From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: daniel.vetter@ffwll.ch, airlied@gmail.com
Cc: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: [PULL] drm-xe-next-fixes
Date: Tue, 16 Jan 2024 11:22:03 +0100 [thread overview]
Message-ID: <20240116102204.106520-1-thomas.hellstrom@linux.intel.com> (raw)
Hi Maintainers,
Various fixes for the Xe driver, as described below, for -rc1.
Thanks,
Thomas
The following changes since commit 315acff5196f4e2f84a2a2d093000e0c6b0b4d1c:
drm/xe: Fix warning on impossible condition (2023-12-26 12:53:26 -0500)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2024-01-16
for you to fetch changes up to bf3ff145df184698a8a80b33265064638572366f:
drm/xe: display support should not depend on EXPERT (2024-01-15 21:40:32 +0100)
----------------------------------------------------------------
Driver Changes:
- Fix for definition of wakeref_t
- Fix for an error code aliasing
- Fix for VM_UNBIND_ALL in the case there are no bound VMAs
- Fixes for a number of __iomem address space mismatches reported by sparse
- Fixes for the assignment of exec_queue priority
- A Fix for skip_guc_pc not taking effect
- Workaround for a build problem on GCC 11
- A couple of fixes for error paths
- Fix a Flat CCS compression metadata copy issue
- Fix a misplace array bounds checking
- Don't have display support depend on EXPERT (as discussed on IRC)
----------------------------------------------------------------
Brian Welty (3):
drm/xe: Fix guc_exec_queue_set_priority
drm/xe: Fix modifying exec_queue priority in xe_migrate_init
drm/xe: Fix bounds checking in __xe_bo_placement_for_flags()
Dan Carpenter (3):
drm/xe/device: clean up on error in probe()
drm/xe/selftests: Fix an error pointer dereference bug
drm/xe: unlock on error path in xe_vm_add_compute_exec_queue()
Jani Nikula (1):
drm/xe: display support should not depend on EXPERT
José Roberto de Souza (1):
drm/xe: Fix definition of intel_wakeref_t
Matthew Brost (1):
drm/xe: Fix exec IOCTL long running exec queue ring full condition
Paul E. McKenney (1):
drm/xe: Fix build bug for GCC 11
Thomas Hellström (6):
drm/xe/vm: Fix an error path
drm/xe: Use __iomem for the regs pointer
drm/xe: Annotate xe_mem_region::mapping with __iomem
drm/xe: Annotate multiple mmio pointers with __iomem
drm/xe: Annotate xe_ttm_stolen_mgr::mapping with __iomem
drm/xe/migrate: Fix CCS copy for small VRAM copy chunks
Vinay Belgaumkar (1):
drm/xe: Check skip_guc_pc before setting SLPC flag
drivers/gpu/drm/xe/Kconfig | 2 +-
drivers/gpu/drm/xe/Makefile | 1 -
.../gpu/drm/xe/compat-i915-headers/intel_wakeref.h | 2 +-
drivers/gpu/drm/xe/tests/xe_bo.c | 5 +-
drivers/gpu/drm/xe/tests/xe_migrate.c | 2 +-
drivers/gpu/drm/xe/xe_bo.c | 16 +--
drivers/gpu/drm/xe/xe_device.c | 2 +-
drivers/gpu/drm/xe/xe_device_types.h | 8 +-
drivers/gpu/drm/xe/xe_exec.c | 7 +-
drivers/gpu/drm/xe/xe_exec_queue.c | 5 +
drivers/gpu/drm/xe/xe_exec_queue_types.h | 6 +-
drivers/gpu/drm/xe/xe_gt_freq.c | 3 +
drivers/gpu/drm/xe/xe_guc.c | 7 +-
drivers/gpu/drm/xe/xe_guc_submit.c | 7 +-
drivers/gpu/drm/xe/xe_migrate.c | 133 +++++++++++++--------
drivers/gpu/drm/xe/xe_mmio.c | 2 +-
drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c | 4 +-
drivers/gpu/drm/xe/xe_vm.c | 15 ++-
18 files changed, 136 insertions(+), 91 deletions(-)
next reply other threads:[~2024-01-16 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 10:22 Thomas Hellström [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 16:35 [PULL] drm-xe-next-fixes 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
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=20240116102204.106520-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.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=lucas.demarchi@intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).