From: Imre Deak <imre.deak@intel.com>
To: "Golani, Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Fix warning callstack for imbalance wakeref
Date: Mon, 29 Aug 2022 17:46:22 +0300 [thread overview]
Message-ID: <YwzRPkKSeeYXWtgn@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <MWHPR11MB1935880C25E9DDF3ED205669B2769@MWHPR11MB1935.namprd11.prod.outlook.com>
On Mon, Aug 29, 2022 at 09:45:53AM +0300, Golani, Mitulkumar Ajitkumar wrote:
> Hi Imre,
>
> > [...]
> > Still not sure what's going. Both i915_pci_probe() and
> > i915_pci_remove()->i915_driver_remove() is called with a runtime PM
> > reference - taken at local_pci_probe() and pci_device_remove() - and so the
> > device should be runtime resumed at those points.
> >
>
> Yes reference is being taken at local_pci_probe() and pci_device_remove() but
> During i915_selftest@perf, it is loading and unloading i915_pci_probe() and
> i915_pci_remove(), here pci_device_remove() is not being called, that's why
> runtime PM reference is not present during i915_driver_remove().
Ok, that explains it. Taking an actual RPM reference unconditionally in
i915_driver_remove() should fix this (instead of the
disable/enable_rpm_wakeref_asserts() calls there):
wakeref = intel_runtime_pm_get();
...
intel_runtime_pm_put(wakeref);
While at it the same change should be applied in i915_driver_release()
as well for consistency.
> > > > > > disable_rpm_wakeref_asserts(rpm);
> > > > > >
> > > > > > intel_opregion_notify_adapter(dev_priv, PCI_D0);
> > > > > > --
> > > > > > 2.25.1
> > > > > >
next prev parent reply other threads:[~2022-08-29 14:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 4:47 [Intel-gfx] [PATCH] drm/i915/display: Fix warning callstack for imbalance wakeref Mitul Golani
2022-08-12 12:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-08-12 19:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-08-16 20:03 ` Patchwork
2022-08-16 20:47 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-08-17 7:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Fix warning callstack for imbalance wakeref (rev2) Patchwork
2022-08-17 9:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Fix warning callstack for imbalance wakeref (rev3) Patchwork
2022-08-17 12:12 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: Fix warning callstack for imbalance wakeref (rev2) Patchwork
2022-08-17 12:49 ` [Intel-gfx] [PATCH] drm/i915/display: Fix warning callstack for imbalance wakeref Imre Deak
2022-08-23 12:39 ` Golani, Mitulkumar Ajitkumar
2022-08-23 12:56 ` Golani, Mitulkumar Ajitkumar
2022-08-25 10:51 ` Imre Deak
2022-08-29 6:45 ` Golani, Mitulkumar Ajitkumar
2022-08-29 14:46 ` Imre Deak [this message]
2022-08-29 16:59 ` Golani, Mitulkumar Ajitkumar
2022-08-17 13:24 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/display: Fix warning callstack for imbalance wakeref (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-08-23 2:35 [Intel-gfx] [PATCH] drm/i915/display: Fix warning callstack for imbalance wakeref Mitul Golani
2022-08-23 11:00 ` Jani Nikula
2022-08-23 5:20 Mitul Golani
2022-08-23 14:31 ` Jani Nikula
2022-08-29 8:31 Mitul Golani
2022-08-30 8:51 Mitul Golani
2022-08-31 11:54 ` Imre Deak
2022-08-31 15:28 ` Andrzej Hajda
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=YwzRPkKSeeYXWtgn@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@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