From: Raag Jadav <raag.jadav@intel.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: rafael@kernel.org, len.brown@intel.com, pavel@ucw.cz,
Jonathan.Cameron@huawei.com, andriy.shevchenko@linux.intel.com,
rf@opensource.cirrus.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
mallikarjunappa.sangannavar@intel.com, bala.senthil@intel.com
Subject: Re: [PATCH v3] PM: Fix symbol export for _SIMPLE_ variants of _PM_OPS()
Date: Wed, 20 Sep 2023 15:07:42 +0300 [thread overview]
Message-ID: <ZQrgjn6uY+B6ZL2j@black.fi.intel.com> (raw)
In-Reply-To: <46a28af1045211edd6c44f7b6aa4c23e7b3a208d.camel@crapouillou.net>
On Wed, Sep 20, 2023 at 12:00:05PM +0200, Paul Cercueil wrote:
> Le mercredi 20 septembre 2023 à 12:33 +0300, Raag Jadav a écrit :
> > On Wed, Sep 20, 2023 at 10:53:23AM +0200, Paul Cercueil wrote:
> > > Le mercredi 20 septembre 2023 à 14:11 +0530, Raag Jadav a écrit :
> > > > Currently EXPORT_*_SIMPLE_DEV_PM_OPS() use EXPORT_*_DEV_PM_OPS()
> > > > set
> > > > of macros to export dev_pm_ops symbol, which export the symbol in
> > > > case
> > > > CONFIG_PM=y but don't take CONFIG_PM_SLEEP into consideration.
> > > >
> > > > Since _SIMPLE_ variants of _PM_OPS() do not include runtime PM
> > > > handles
> > > > and are only used in case CONFIG_PM_SLEEP=y, we should not be
> > > > exporting
> > > > their dev_pm_ops symbol in case CONFIG_PM_SLEEP=n.
> > > >
> > > > This can be fixed by having two distinct set of export macros for
> > > > both
> > > > _RUNTIME_ and _SIMPLE_ variants of _PM_OPS(), such that the
> > > > export of
> > > > dev_pm_ops symbol used in each variant depends on CONFIG_PM and
> > > > CONFIG_PM_SLEEP respectively.
> > > >
> > > > Introduce _DEV_SLEEP_PM_OPS() set of export macros for _SIMPLE_
> > > > variants
> > > > of _PM_OPS(), which export dev_pm_ops symbol only in case
> > > > CONFIG_PM_SLEEP=y
> > > > and discard it otherwise.
> > > >
> > > > Fixes: 34e1ed189fab ("PM: Improve EXPORT_*_DEV_PM_OPS macros")
> > > > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > > > ---
> > > > PS: This is a standalone fix and works without updating any
> > > > drivers.
> > >
> > > I had to double-check that, to make sure that none of the drivers
> > > using
> > > these macros also use pm_ptr() instead of pm_sleep_ptr() to access
> > > the
> > > exported dev_pm_ops.
> > >
> > > I did not check extensively but everything seems to use
> > > pm_sleep_ptr(),
> > > so it looks safe enough.
> >
> > I have tested it against -rc2 without any problems.
>
> You'd need to test an "allyesconfig" with CONFIG_PM=y, and
> CONFIG_PM_SLEEP disabled. Is that what you tested?
Yes, and also validated *.symvers if dev_pm_ops symbol is really discarded.
Seems to work as expected.
Raag
prev parent reply other threads:[~2023-09-20 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 8:41 [PATCH v3] PM: Fix symbol export for _SIMPLE_ variants of _PM_OPS() Raag Jadav
2023-09-20 8:53 ` Paul Cercueil
2023-09-20 9:33 ` Raag Jadav
2023-09-20 10:00 ` Paul Cercueil
2023-09-20 12:07 ` Raag Jadav [this message]
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=ZQrgjn6uY+B6ZL2j@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bala.senthil@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=paul@crapouillou.net \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rf@opensource.cirrus.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