From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Badal Nilawar <badal.nilawar@intel.com>,
Andi Shyti <andi.shyti@intel.com>
Subject: Re: [PATCH] drm/i915: Don't enable hwmon for selftests
Date: Thu, 11 Apr 2024 13:47:13 +0300 [thread overview]
Message-ID: <Zhe_sRPLB7Dn7-tO@intel.com> (raw)
In-Reply-To: <85pluwjxir.wl-ashutosh.dixit@intel.com>
On Wed, Apr 10, 2024 at 10:09:32PM -0700, Dixit, Ashutosh wrote:
> On Wed, 10 Apr 2024 04:42:46 -0700, Ville Syrjälä wrote:
> >
> > On Tue, Apr 09, 2024 at 09:28:55PM -0700, Ashutosh Dixit wrote:
> > > There are no hwmon selftests so there is no need to enable hwmon for
> > > selftests. So enable hwmon only for real driver load.
> > >
> > > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/10366
> > > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> >
> > Why are we adding duct tape instead of fixing it properly?
>
> Yeah pretty much what I said here myself:
>
> https://patchwork.freedesktop.org/patch/588585/?series=132243&rev=1#comment_1071014
>
> The issue has been difficult to root-cause. My last effort can be seen here:
>
> https://patchwork.freedesktop.org/patch/584859/?series=131630&rev=1#comment_1067888
>
> Though Badal went further and saw that occasionaly the memory would get
> freed first and hwmon would get unregistered as much as 2 seconds later,
> which will cause the crash if anyone touched hwmon sysfs in those final 2
> seconds. So not sure what is causing that 2 second delay.
Sounds like someone holding a sysfs file/etc. open. Should be trivial
to do that by hand and see what happens.
>
> I am not sure if it is worth root-causing further. I am pretty sure if we
> get rid of the devm_ stuff, that will fix the issue too. So if this patch
> is not acceptable, we could just go that route (get rid of devm_ in hwmon).
>
> Thanks.
> --
> Ashutosh
>
> > > ---
> > > drivers/gpu/drm/i915/i915_driver.c | 16 ++++++++++++++--
> > > 1 file changed, 14 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > > index 9ee902d5b72c..6fa6d2c8109f 100644
> > > --- a/drivers/gpu/drm/i915/i915_driver.c
> > > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > > @@ -94,6 +94,7 @@
> > > #include "i915_memcpy.h"
> > > #include "i915_perf.h"
> > > #include "i915_query.h"
> > > +#include "i915_selftest.h"
> > > #include "i915_suspend.h"
> > > #include "i915_switcheroo.h"
> > > #include "i915_sysfs.h"
> > > @@ -589,6 +590,15 @@ static void i915_driver_hw_remove(struct drm_i915_private *dev_priv)
> > > pci_disable_msi(pdev);
> > > }
> > >
> > > +static bool is_selftest(void)
> > > +{
> > > +#if IS_ENABLED(CONFIG_DRM_I915_SELFTEST)
> > > + return i915_selftest.live || i915_selftest.perf || i915_selftest.mock;
> > > +#else
> > > + return false;
> > > +#endif
> > > +}
> > > +
> > > /**
> > > * i915_driver_register - register the driver with the rest of the system
> > > * @dev_priv: device private
> > > @@ -624,7 +634,8 @@ static void i915_driver_register(struct drm_i915_private *dev_priv)
> > >
> > > intel_pxp_debugfs_register(dev_priv->pxp);
> > >
> > > - i915_hwmon_register(dev_priv);
> > > + if (!is_selftest())
> > > + i915_hwmon_register(dev_priv);
> > >
> > > intel_display_driver_register(dev_priv);
> > >
> > > @@ -660,7 +671,8 @@ static void i915_driver_unregister(struct drm_i915_private *dev_priv)
> > > for_each_gt(gt, dev_priv, i)
> > > intel_gt_driver_unregister(gt);
> > >
> > > - i915_hwmon_unregister(dev_priv);
> > > + if (!is_selftest())
> > > + i915_hwmon_unregister(dev_priv);
> > >
> > > i915_perf_unregister(dev_priv);
> > > i915_pmu_unregister(dev_priv);
> > > --
> > > 2.41.0
> >
> > --
> > Ville Syrjälä
> > Intel
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-04-11 10:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 4:28 [PATCH] drm/i915: Don't enable hwmon for selftests Ashutosh Dixit
2024-04-10 4:37 ` Dixit, Ashutosh
2024-04-10 4:56 ` Nilawar, Badal
2024-04-10 5:26 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-04-10 11:42 ` [PATCH] " Ville Syrjälä
2024-04-11 5:09 ` Dixit, Ashutosh
2024-04-11 10:47 ` Ville Syrjälä [this message]
2024-04-13 0:35 ` Dixit, Ashutosh
2024-04-13 0:37 ` Dixit, Ashutosh
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 4:58 Ashutosh Dixit
2024-04-10 5:17 ` Nilawar, Badal
2024-04-10 6:06 ` Dixit, Ashutosh
2024-04-10 6:05 Ashutosh Dixit
2024-04-10 6:45 ` Nilawar, Badal
2024-04-10 13:53 ` Andi Shyti
2024-04-11 4:59 ` Dixit, Ashutosh
2024-04-10 20:07 Ashutosh Dixit
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=Zhe_sRPLB7Dn7-tO@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=andi.shyti@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-gfx@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