From: Andi Shyti <andi.shyti@linux.intel.com>
To: Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>
Subject: [Intel-gfx] [PATCH v5 06/11] drm/i915/gvt: Use to_gt() helper
Date: Mon, 6 Dec 2021 02:48:56 +0200 [thread overview]
Message-ID: <20211206004901.69729-7-andi.shyti@linux.intel.com> (raw)
In-Reply-To: <20211206004901.69729-1-andi.shyti@linux.intel.com>
From: Michał Winiarski <michal.winiarski@intel.com>
Use to_gt() helper consistently throughout the codebase.
Pure mechanical s/i915->gt/to_gt(i915). No functional changes.
Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
---
drivers/gpu/drm/i915/gvt/gvt.c | 2 +-
drivers/gpu/drm/i915/gvt/scheduler.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gvt/gvt.c b/drivers/gpu/drm/i915/gvt/gvt.c
index cbac409f6c8a..f0b69e4dcb52 100644
--- a/drivers/gpu/drm/i915/gvt/gvt.c
+++ b/drivers/gpu/drm/i915/gvt/gvt.c
@@ -205,7 +205,7 @@ int intel_gvt_init_device(struct drm_i915_private *i915)
spin_lock_init(&gvt->scheduler.mmio_context_lock);
mutex_init(&gvt->lock);
mutex_init(&gvt->sched_lock);
- gvt->gt = &i915->gt;
+ gvt->gt = to_gt(i915);
i915->gvt = gvt;
init_device_info(gvt);
diff --git a/drivers/gpu/drm/i915/gvt/scheduler.c b/drivers/gpu/drm/i915/gvt/scheduler.c
index 6c804102528b..42a0c9ae0a73 100644
--- a/drivers/gpu/drm/i915/gvt/scheduler.c
+++ b/drivers/gpu/drm/i915/gvt/scheduler.c
@@ -1386,7 +1386,7 @@ int intel_vgpu_setup_submission(struct intel_vgpu *vgpu)
enum intel_engine_id i;
int ret;
- ppgtt = i915_ppgtt_create(&i915->gt, I915_BO_ALLOC_PM_EARLY);
+ ppgtt = i915_ppgtt_create(to_gt(i915), I915_BO_ALLOC_PM_EARLY);
if (IS_ERR(ppgtt))
return PTR_ERR(ppgtt);
--
2.34.1
next prev parent reply other threads:[~2021-12-06 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 0:48 [Intel-gfx] [PATCH v5 00/11] More preparation for multi gt patches Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 01/11] drm/i915: Store backpointer to GT in uncore Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 02/11] drm/i915: Introduce to_gt() helper Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 03/11] drm/i915/display: Use " Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 04/11] drm/i915/gt: " Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 05/11] drm/i915/gem: " Andi Shyti
2021-12-06 0:48 ` Andi Shyti [this message]
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 07/11] drm/i915/selftests: " Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 08/11] drm/i915/pxp: " Andi Shyti
2021-12-06 0:48 ` [Intel-gfx] [PATCH v5 09/11] drm/i915: " Andi Shyti
2021-12-06 0:49 ` [Intel-gfx] [PATCH v5 10/11] drm/i915: Use to_gt() helper for GGTT accesses Andi Shyti
2021-12-06 0:49 ` [Intel-gfx] [PATCH v5 11/11] drm/i915: Rename i915->gt to i915->gt0 Andi Shyti
2021-12-06 11:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for More preparation for multi gt patches (rev5) Patchwork
2021-12-06 11:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-06 12:07 ` [Intel-gfx] ✗ Fi.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=20211206004901.69729-7-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michal.winiarski@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