Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>
Subject: [Intel-xe] [PATCH v3 0/4] drm/xe: Assorted memory-management fixes
Date: Fri, 24 Nov 2023 10:11:07 +0100	[thread overview]
Message-ID: <20231124091111.77269-1-thomas.hellstrom@linux.intel.com> (raw)

The patch series addresses items 1, 2, 3, 6 and 7, in the from

https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/946

v2:
- Address a review comment in patch 1 (Matthew Auld)
- Add extra asid allocation debugging on CONFIG_DRM_XE_DEBUG
v3:
- Stricter return value checking for xa_alloc_cyclic() in patch 4.

Cc: Ohad Sharabi <osharabi@habana.ai>

Thomas Hellström (4):
  drm/xe: Ensure that we don't access the placements array out-of-bounds
  drm/xe/bo: Rename xe_bo_get_sg() to xe_bo_sg()
  drm/xe/bo: Remove leftover trace_printk()
  drm/xe/vm: Fix ASID XA usage

 drivers/gpu/drm/xe/tests/xe_migrate.c |  2 +-
 drivers/gpu/drm/xe/xe_bo.c            | 19 ++++++++++++-------
 drivers/gpu/drm/xe/xe_bo.h            |  2 +-
 drivers/gpu/drm/xe/xe_device.c        |  2 +-
 drivers/gpu/drm/xe/xe_migrate.c       |  8 ++++----
 drivers/gpu/drm/xe/xe_pt.c            |  2 +-
 drivers/gpu/drm/xe/xe_vm.c            |  5 +++--
 7 files changed, 23 insertions(+), 17 deletions(-)

-- 
2.41.0



Thomas Hellström (4):
  drm/xe: Ensure that we don't access the placements array out-of-bounds
  drm/xe/bo: Rename xe_bo_get_sg() to xe_bo_sg()
  drm/xe/bo: Remove leftover trace_printk()
  drm/xe/vm: Fix ASID XA usage

 drivers/gpu/drm/xe/tests/xe_migrate.c |  2 +-
 drivers/gpu/drm/xe/xe_bo.c            | 44 +++++++++++++++------------
 drivers/gpu/drm/xe/xe_bo.h            |  2 +-
 drivers/gpu/drm/xe/xe_device.c        | 15 ++++++++-
 drivers/gpu/drm/xe/xe_migrate.c       |  8 ++---
 drivers/gpu/drm/xe/xe_pt.c            |  2 +-
 drivers/gpu/drm/xe/xe_vm.c            |  5 +--
 7 files changed, 48 insertions(+), 30 deletions(-)

-- 
2.41.0



Thomas Hellström (4):
  drm/xe: Ensure that we don't access the placements array out-of-bounds
  drm/xe/bo: Rename xe_bo_get_sg() to xe_bo_sg()
  drm/xe/bo: Remove leftover trace_printk()
  drm/xe/vm: Fix ASID XA usage

 drivers/gpu/drm/xe/tests/xe_migrate.c |  2 +-
 drivers/gpu/drm/xe/xe_bo.c            | 44 +++++++++++++++------------
 drivers/gpu/drm/xe/xe_bo.h            |  2 +-
 drivers/gpu/drm/xe/xe_device.c        | 15 ++++++++-
 drivers/gpu/drm/xe/xe_migrate.c       |  8 ++---
 drivers/gpu/drm/xe/xe_pt.c            |  2 +-
 drivers/gpu/drm/xe/xe_vm.c            |  5 +--
 7 files changed, 48 insertions(+), 30 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-11-24  9:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24  9:11 Thomas Hellström [this message]
2023-11-24  9:11 ` [Intel-xe] [PATCH v3 1/4] drm/xe: Ensure that we don't access the placements array out-of-bounds Thomas Hellström
2023-11-24  9:11 ` [Intel-xe] [PATCH v3 2/4] drm/xe/bo: Rename xe_bo_get_sg() to xe_bo_sg() Thomas Hellström
2023-11-24  9:11 ` [Intel-xe] [PATCH v3 3/4] drm/xe/bo: Remove leftover trace_printk() Thomas Hellström
2023-11-24  9:11 ` [Intel-xe] [PATCH v3 4/4] drm/xe/vm: Fix ASID XA usage Thomas Hellström
2023-11-24 11:11   ` Matthew Auld
2023-11-24 11:13     ` Thomas Hellström
2023-11-24 10:23 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Assorted memory-management fixes (rev3) Patchwork
2023-11-24 10:24 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-24 10:25 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-24 10:32 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-24 10:33 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-24 10:34 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-24 11:08 ` [Intel-xe] ✓ CI.BAT: " 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=20231124091111.77269-1-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    /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