Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI v3 15/18] drm/xe: reset mmio mappings with devm
Date: Wed, 22 May 2024 11:21:58 +0100	[thread overview]
Message-ID: <20240522102143.128069-33-matthew.auld@intel.com> (raw)
In-Reply-To: <20240522102143.128069-19-matthew.auld@intel.com>

Set our various mmio mappings to NULL. This should make it easier to
catch something rogue trying to mess with mmio after device removal. For
example, we might unmap everything and then start hitting some mmio
address which has already been unmamped by us and then remapped by
something else, causing all kinds of carnage.

Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/xe/xe_device.c |  4 +++-
 drivers/gpu/drm/xe/xe_mmio.c   | 35 ++++++++++++++++++++++++++++------
 drivers/gpu/drm/xe/xe_mmio.h   |  2 +-
 3 files changed, 33 insertions(+), 8 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
index 49ea1ba340e6..a9c1f353c2ad 100644
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@ -554,7 +554,9 @@ int xe_device_probe(struct xe_device *xe)
 	if (err)
 		return err;
 
-	xe_mmio_probe_tiles(xe);
+	err = xe_mmio_probe_tiles(xe);
+	if (err)
+		return err;
 
 	xe_ttm_sys_mgr_init(xe);
 
diff --git a/drivers/gpu/drm/xe/xe_mmio.c b/drivers/gpu/drm/xe/xe_mmio.c
index a3094e741db8..0ad840bab8f3 100644
--- a/drivers/gpu/drm/xe/xe_mmio.c
+++ b/drivers/gpu/drm/xe/xe_mmio.c
@@ -255,6 +255,21 @@ static int xe_mmio_tile_vram_size(struct xe_tile *tile, u64 *vram_size,
 	return xe_force_wake_put(gt_to_fw(gt), XE_FW_GT);
 }
 
+static void vram_fini(void *arg)
+{
+	struct xe_device *xe = arg;
+	struct xe_tile *tile;
+	int id;
+
+	if (xe->mem.vram.mapping)
+		iounmap(xe->mem.vram.mapping);
+
+	xe->mem.vram.mapping = NULL;
+
+	for_each_tile(tile, xe, id)
+		tile->mem.vram.mapping = NULL;
+}
+
 int xe_mmio_probe_vram(struct xe_device *xe)
 {
 	struct xe_tile *tile;
@@ -331,10 +346,20 @@ int xe_mmio_probe_vram(struct xe_device *xe)
 	drm_info(&xe->drm, "Available VRAM: %pa, %pa\n", &xe->mem.vram.io_start,
 		 &available_size);
 
-	return 0;
+	return devm_add_action_or_reset(xe->drm.dev, vram_fini, xe);
 }
 
-void xe_mmio_probe_tiles(struct xe_device *xe)
+static void tiles_fini(void *arg)
+{
+	struct xe_device *xe = arg;
+	struct xe_tile *tile;
+	int id;
+
+	for_each_tile(tile, xe, id)
+		tile->mmio.regs = NULL;
+}
+
+int xe_mmio_probe_tiles(struct xe_device *xe)
 {
 	size_t tile_mmio_size = SZ_16M, tile_mmio_ext_size = xe->info.tile_mmio_ext_size;
 	u8 id, tile_count = xe->info.tile_count;
@@ -385,6 +410,8 @@ void xe_mmio_probe_tiles(struct xe_device *xe)
 			regs += tile_mmio_ext_size;
 		}
 	}
+
+	return devm_add_action_or_reset(xe->drm.dev, tiles_fini, xe);
 }
 
 static void mmio_fini(void *arg)
@@ -392,10 +419,6 @@ static void mmio_fini(void *arg)
 	struct xe_device *xe = arg;
 
 	pci_iounmap(to_pci_dev(xe->drm.dev), xe->mmio.regs);
-	if (xe->mem.vram.mapping)
-		iounmap(xe->mem.vram.mapping);
-
-	xe->mem.vram.mapping = NULL;
 	xe->mmio.regs = NULL;
 }
 
diff --git a/drivers/gpu/drm/xe/xe_mmio.h b/drivers/gpu/drm/xe/xe_mmio.h
index 445ec6a0753e..6488705c1ffe 100644
--- a/drivers/gpu/drm/xe/xe_mmio.h
+++ b/drivers/gpu/drm/xe/xe_mmio.h
@@ -21,7 +21,7 @@ struct xe_device;
 #define LMEM_BAR		2
 
 int xe_mmio_init(struct xe_device *xe);
-void xe_mmio_probe_tiles(struct xe_device *xe);
+int xe_mmio_probe_tiles(struct xe_device *xe);
 
 u8 xe_mmio_read8(struct xe_gt *gt, struct xe_reg reg);
 u16 xe_mmio_read16(struct xe_gt *gt, struct xe_reg reg);
-- 
2.45.1


  parent reply	other threads:[~2024-05-22 10:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 10:21 [CI v3 01/18] drm/xe/pci: remove broken driver_release Matthew Auld
2024-05-22 10:21 ` [CI v3 02/18] drm/xe: covert sysfs over to devm Matthew Auld
2024-05-22 10:21 ` [CI v3 03/18] drm/xe/ggtt: use drm_dev_enter to mark device section Matthew Auld
2024-05-22 10:21 ` [CI v3 04/18] drm/xe/guc: move guc_fini over to devm Matthew Auld
2024-05-22 10:21 ` [CI v3 05/18] drm/xe/guc: s/guc_fini/guc_fini_hw/ Matthew Auld
2024-05-22 10:21 ` [CI v3 06/18] drm/xe/guc_pc: move pc_fini to devm Matthew Auld
2024-05-22 10:21 ` [CI v3 07/18] drm/xe/guc_pc: s/pc_fini/pc_fini_hw/ Matthew Auld
2024-05-22 10:21 ` [CI v3 08/18] drm/xe/irq: move irq_uninstall over to devm Matthew Auld
2024-05-22 10:21 ` [CI v3 09/18] drm/xe/device: move flr " Matthew Auld
2024-05-22 10:21 ` [CI v3 10/18] drm/xe/device: move xe_device_sanitize over " Matthew Auld
2024-05-22 10:21 ` [CI v3 11/18] drm/xe/coredump: move " Matthew Auld
2024-05-22 10:21 ` [CI v3 12/18] drm/xe/gt: break out gt_fini into sw vs hw state Matthew Auld
2024-05-22 10:21 ` [CI v3 13/18] drm/xe: make gt_remove use devm Matthew Auld
2024-05-22 10:21 ` [CI v3 14/18] drm/xe/mmio: move mmio_fini over to devm Matthew Auld
2024-05-22 10:21 ` Matthew Auld [this message]
2024-05-22 10:21 ` [CI v3 16/18] drm/xe/display: move display fini stuff " Matthew Auld
2024-05-22 10:22 ` [CI v3 17/18] drm/xe/display: stop calling domains_driver_remove twice Matthew Auld
2024-05-22 10:22 ` [CI v3 18/18] drm/xe/display: move device_remove over to drmm Matthew Auld
2024-05-22 10:28 ` ✓ CI.Patch_applied: success for series starting with [CI,v3,01/18] drm/xe/pci: remove broken driver_release Patchwork
2024-05-22 10:28 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-22 10:29 ` ✓ CI.KUnit: success " Patchwork
2024-05-22 10:41 ` ✓ CI.Build: " Patchwork
2024-05-22 10:43 ` ✗ CI.Hooks: failure " Patchwork
2024-05-22 10:45 ` ✓ CI.checksparse: success " Patchwork
2024-05-22 11:36 ` ✗ CI.BAT: failure " Patchwork
2024-05-22 13:44 ` ✗ CI.FULL: " 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=20240522102143.128069-33-matthew.auld@intel.com \
    --to=matthew.auld@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