From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 09/14] drm/i915: Handle each GT on init/release and suspend/resume
Date: Thu, 8 Sep 2022 13:55:08 -0700 [thread overview]
Message-ID: <a57ddc3e-d706-22bb-9338-4f8835f6538e@intel.com> (raw)
In-Reply-To: <20220906234934.3655440-10-matthew.d.roper@intel.com>
On 9/6/2022 4:49 PM, Matt Roper wrote:
> In preparation for enabling a second GT, there are a number of GT/uncore
> operations that happen during initialization or suspend flows that need
> to be performed on each GT, not just the primary,
>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/i915/i915_driver.c | 59 +++++++++++++++++++++---------
> 1 file changed, 42 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> index bb9ba1aed1bb..e5c3cf5045d4 100644
> --- a/drivers/gpu/drm/i915/i915_driver.c
> +++ b/drivers/gpu/drm/i915/i915_driver.c
> @@ -310,8 +310,13 @@ static void intel_detect_preproduction_hw(struct drm_i915_private *dev_priv)
>
> static void sanitize_gpu(struct drm_i915_private *i915)
> {
> - if (!INTEL_INFO(i915)->gpu_reset_clobbers_display)
> - __intel_gt_reset(to_gt(i915), ALL_ENGINES);
> + if (!INTEL_INFO(i915)->gpu_reset_clobbers_display) {
> + struct intel_gt *gt;
> + unsigned int i;
> +
> + for_each_gt(gt, i915, i)
> + __intel_gt_reset(gt, ALL_ENGINES);
> + }
> }
>
> /**
> @@ -730,6 +735,8 @@ static void i915_driver_hw_remove(struct drm_i915_private *dev_priv)
> static void i915_driver_register(struct drm_i915_private *dev_priv)
> {
> struct drm_device *dev = &dev_priv->drm;
> + struct intel_gt *gt;
> + unsigned int i;
>
> i915_gem_driver_register(dev_priv);
> i915_pmu_register(dev_priv);
> @@ -749,7 +756,8 @@ static void i915_driver_register(struct drm_i915_private *dev_priv)
> /* Depends on sysfs having been initialized */
> i915_perf_register(dev_priv);
>
> - intel_gt_driver_register(to_gt(dev_priv));
> + for_each_gt(gt, dev_priv, i)
> + intel_gt_driver_register(gt);
>
> intel_display_driver_register(dev_priv);
>
> @@ -768,6 +776,9 @@ static void i915_driver_register(struct drm_i915_private *dev_priv)
> */
> static void i915_driver_unregister(struct drm_i915_private *dev_priv)
> {
> + struct intel_gt *gt;
> + unsigned int i;
> +
> i915_switcheroo_unregister(dev_priv);
>
> intel_unregister_dsm_handler();
> @@ -777,7 +788,8 @@ static void i915_driver_unregister(struct drm_i915_private *dev_priv)
>
> intel_display_driver_unregister(dev_priv);
>
> - intel_gt_driver_unregister(to_gt(dev_priv));
> + for_each_gt(gt, dev_priv, i)
> + intel_gt_driver_unregister(gt);
>
> i915_perf_unregister(dev_priv);
> i915_pmu_unregister(dev_priv);
> @@ -799,6 +811,8 @@ static void i915_welcome_messages(struct drm_i915_private *dev_priv)
> {
> if (drm_debug_enabled(DRM_UT_DRIVER)) {
> struct drm_printer p = drm_debug_printer("i915 device info:");
> + struct intel_gt *gt;
> + unsigned int i;
>
> drm_printf(&p, "pciid=0x%04x rev=0x%02x platform=%s (subplatform=0x%x) gen=%i\n",
> INTEL_DEVID(dev_priv),
> @@ -811,7 +825,8 @@ static void i915_welcome_messages(struct drm_i915_private *dev_priv)
> intel_device_info_print(INTEL_INFO(dev_priv),
> RUNTIME_INFO(dev_priv), &p);
> i915_print_iommu_status(dev_priv, &p);
> - intel_gt_info_print(&to_gt(dev_priv)->info, &p);
> + for_each_gt(gt, dev_priv, i)
> + intel_gt_info_print(>->info, &p);
> }
>
> if (IS_ENABLED(CONFIG_DRM_I915_DEBUG))
> @@ -1230,13 +1245,15 @@ static int i915_drm_suspend_late(struct drm_device *dev, bool hibernation)
> struct drm_i915_private *dev_priv = to_i915(dev);
> struct pci_dev *pdev = to_pci_dev(dev_priv->drm.dev);
> struct intel_runtime_pm *rpm = &dev_priv->runtime_pm;
> - int ret;
> + struct intel_gt *gt;
> + int ret, i;
>
> disable_rpm_wakeref_asserts(rpm);
>
> i915_gem_suspend_late(dev_priv);
>
> - intel_uncore_suspend(&dev_priv->uncore);
> + for_each_gt(gt, dev_priv, i)
> + intel_uncore_suspend(gt->uncore);
>
> intel_power_domains_suspend(dev_priv,
> get_suspend_mode(dev_priv, hibernation));
> @@ -1368,7 +1385,8 @@ static int i915_drm_resume_early(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = to_i915(dev);
> struct pci_dev *pdev = to_pci_dev(dev_priv->drm.dev);
> - int ret;
> + struct intel_gt *gt;
> + int ret, i;
>
> /*
> * We have a resume ordering issue with the snd-hda driver also
> @@ -1422,9 +1440,10 @@ static int i915_drm_resume_early(struct drm_device *dev)
> drm_err(&dev_priv->drm,
> "Resume prepare failed: %d, continuing anyway\n", ret);
>
> - intel_uncore_resume_early(&dev_priv->uncore);
> -
> - intel_gt_check_and_clear_faults(to_gt(dev_priv));
> + for_each_gt(gt, dev_priv, i) {
> + intel_uncore_resume_early(gt->uncore);
> + intel_gt_check_and_clear_faults(gt);
> + }
>
> intel_display_power_resume_early(dev_priv);
>
> @@ -1604,7 +1623,8 @@ static int intel_runtime_suspend(struct device *kdev)
> {
> struct drm_i915_private *dev_priv = kdev_to_i915(kdev);
> struct intel_runtime_pm *rpm = &dev_priv->runtime_pm;
> - int ret;
> + struct intel_gt *gt;
> + int ret, i;
>
> if (drm_WARN_ON_ONCE(&dev_priv->drm, !HAS_RUNTIME_PM(dev_priv)))
> return -ENODEV;
> @@ -1619,11 +1639,13 @@ static int intel_runtime_suspend(struct device *kdev)
> */
> i915_gem_runtime_suspend(dev_priv);
>
> - intel_gt_runtime_suspend(to_gt(dev_priv));
> + for_each_gt(gt, dev_priv, i)
> + intel_gt_runtime_suspend(gt);
>
> intel_runtime_pm_disable_interrupts(dev_priv);
>
> - intel_uncore_suspend(&dev_priv->uncore);
> + for_each_gt(gt, dev_priv, i)
> + intel_uncore_suspend(gt->uncore);
>
> intel_display_power_suspend(dev_priv);
>
> @@ -1687,7 +1709,8 @@ static int intel_runtime_resume(struct device *kdev)
> {
> struct drm_i915_private *dev_priv = kdev_to_i915(kdev);
> struct intel_runtime_pm *rpm = &dev_priv->runtime_pm;
> - int ret;
> + struct intel_gt *gt;
> + int ret, i;
>
> if (drm_WARN_ON_ONCE(&dev_priv->drm, !HAS_RUNTIME_PM(dev_priv)))
> return -ENODEV;
> @@ -1707,7 +1730,8 @@ static int intel_runtime_resume(struct device *kdev)
>
> ret = vlv_resume_prepare(dev_priv, true);
>
> - intel_uncore_runtime_resume(&dev_priv->uncore);
> + for_each_gt(gt, dev_priv, i)
> + intel_uncore_runtime_resume(gt->uncore);
>
> intel_runtime_pm_enable_interrupts(dev_priv);
>
> @@ -1715,7 +1739,8 @@ static int intel_runtime_resume(struct device *kdev)
> * No point of rolling back things in case of an error, as the best
> * we can do is to hope that things will still work (and disable RPM).
> */
> - intel_gt_runtime_resume(to_gt(dev_priv));
> + for_each_gt(gt, dev_priv, i)
> + intel_gt_runtime_resume(gt);
>
> /*
> * On VLV/CHV display interrupts are part of the display
next prev parent reply other threads:[~2022-09-08 20:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 23:49 [Intel-gfx] [PATCH v3 00/14] i915: Add "standalone media" support for MTL Matt Roper
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 01/14] drm/i915: Move locking and unclaimed check into mmio_debug_{suspend, resume} Matt Roper
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 02/14] drm/i915: Only hook up uncore->debug for primary uncore Matt Roper
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 03/14] drm/i915: Use managed allocations for extra uncore objects Matt Roper
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 04/14] drm/i915: Drop intel_gt_tile_cleanup() Matt Roper
2022-09-07 0:07 ` Lucas De Marchi
2022-09-07 11:18 ` kernel test robot
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 05/14] drm/i915: Prepare more multi-GT initialization Matt Roper
2022-09-08 16:19 ` Iddamsetty, Aravind
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 06/14] drm/i915: Rename and expose common GT early init routine Matt Roper
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 07/14] drm/i915: Use a DRM-managed action to release the PCI bridge device Matt Roper
2022-09-09 20:57 ` Sripada, Radhakrishna
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 08/14] drm/i915: Initialize MMIO access for each GT Matt Roper
2022-09-08 20:52 ` Ceraolo Spurio, Daniele
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 09/14] drm/i915: Handle each GT on init/release and suspend/resume Matt Roper
2022-09-08 20:55 ` Ceraolo Spurio, Daniele [this message]
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 10/14] drm/i915/uncore: Add GSI offset to uncore Matt Roper
2022-09-08 21:16 ` Ceraolo Spurio, Daniele
2022-09-08 22:29 ` Matt Roper
2022-09-08 22:45 ` [Intel-gfx] [PATCH v3.1 " Matt Roper
2022-09-08 22:53 ` Ceraolo Spurio, Daniele
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 11/14] drm/i915/mtl: Add gsi_offset when emitting aux table invalidation Matt Roper
2022-09-07 16:16 ` Iddamsetty, Aravind
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 12/14] drm/i915/xelpmp: Expose media as another GT Matt Roper
2022-09-08 16:22 ` Iddamsetty, Aravind
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 13/14] drm/i915/mtl: Use primary GT's irq lock for media GT Matt Roper
2022-09-08 21:20 ` Ceraolo Spurio, Daniele
2022-09-06 23:49 ` [Intel-gfx] [PATCH v3 14/14] drm/i915/mtl: Hook up interrupts for standalone media Matt Roper
2022-09-07 0:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: Add "standalone media" support for MTL (rev4) Patchwork
2022-09-07 0:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-07 0:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-07 4:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-07 5:27 ` Matt Roper
2022-09-07 15:46 ` Vudum, Lakshminarayana
2022-09-07 15:27 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-09-08 23:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: Add "standalone media" support for MTL (rev5) Patchwork
2022-09-08 23:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-08 23:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-09 5:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-09 22:21 ` Matt Roper
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=a57ddc3e-d706-22bb-9338-4f8835f6538e@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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