Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw.linux@gmail.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Subject: Re: [PATCH 2/2] drm/i915: Add intel_gvt_driver_remove() onto error cleanup path
Date: Sat, 06 Dec 2025 22:41:33 +0900	[thread overview]
Message-ID: <87y0nfiv76.fsf@dell-wzy> (raw)
In-Reply-To: <20251201161013.735943-3-juhapekka.heikkila@gmail.com>

Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com> writes:

> Add intel_gvt_driver_remove() onto error cleanup path.
>
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
>  drivers/gpu/drm/i915/i915_driver.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> index 0128faf2e483..f8c01d52aba8 100644
> --- a/drivers/gpu/drm/i915/i915_driver.c
> +++ b/drivers/gpu/drm/i915/i915_driver.c
> @@ -908,6 +908,7 @@ int i915_driver_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>  	i915_gem_drain_freed_objects(i915);
>  	i915_ggtt_driver_late_release(i915);
>  out_cleanup_mmio:
> +	intel_gvt_driver_remove(i915);
>  	i915_driver_mmio_release(i915);
>  out_runtime_pm_put:
>  	enable_rpm_wakeref_asserts(&i915->runtime_pm);
> -- 

It might be the simplest way to fix, or even better to clean up it by
moving intel_gvt_driver_remove() into i915_driver_hw_remove(), so
they're more paired with i915_driver_hw_probe() and move this fix into
hw_probe() as well, anyway...

Reviewed-by: Zhenyu Wang <zhenyuw.linux@gmail.com>


  reply	other threads:[~2025-12-06 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 16:10 [PATCH 0/2] switch to use kernel standard fault injection in i915 Juha-Pekka Heikkila
2025-12-01 16:10 ` [PATCH 1/2] drm/i915: switch to use kernel standard error injection Juha-Pekka Heikkila
2025-12-12 12:41   ` Jani Nikula
2025-12-01 16:10 ` [PATCH 2/2] drm/i915: Add intel_gvt_driver_remove() onto error cleanup path Juha-Pekka Heikkila
2025-12-06 13:41   ` Zhenyu Wang [this message]
2025-12-01 17:56 ` ✓ CI.KUnit: success for Switch to use kernel standard fault injection in i915 (rev6) Patchwork
2025-12-01 18:11 ` ✗ CI.checksparse: warning " Patchwork
2025-12-01 18:57 ` ✓ Xe.CI.BAT: success " Patchwork
2025-12-01 21:48 ` ✓ Xe.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-12-16  8:07 [PATCH 0/2] switch to use kernel standard fault injection in i915 Juha-Pekka Heikkila
2025-12-16  8:07 ` [PATCH 2/2] drm/i915: Add intel_gvt_driver_remove() onto error cleanup path Juha-Pekka Heikkila
2025-12-01 13:05 [PATCH 0/2] switch to use kernel standard fault injection in i915 Juha-Pekka Heikkila
2025-12-01 13:05 ` [PATCH 2/2] drm/i915: Add intel_gvt_driver_remove() onto error cleanup path Juha-Pekka Heikkila
2025-12-01 12:00 [PATCH 0/2] witch to use kernel standard fault injection in i915 Juha-Pekka Heikkila
2025-12-01 12:00 ` [PATCH 2/2] drm/i915: Add intel_gvt_driver_remove() onto error cleanup path Juha-Pekka Heikkila

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=87y0nfiv76.fsf@dell-wzy \
    --to=zhenyuw.linux@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.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