From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
markgross@kernel.org, ilpo.jarvinen@linux.intel.com,
andriy.shevchenko@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [UPDATE][PATCH] platform/x86/intel-uncore-freq: Conditionally create attribute for read frequency
Date: Thu, 05 Oct 2023 07:07:58 -0700 [thread overview]
Message-ID: <5dda866185a286e61f949a48e04ff1ea6b3a5b03.camel@linux.intel.com> (raw)
In-Reply-To: <e84bc80e-1fd9-f07b-526a-b4eb4780ea9b@redhat.com>
Hi Hans,
On Thu, 2023-10-05 at 09:03 +0200, Hans de Goede wrote:
> Hi Srinivas,
>
> On 10/4/23 20:19, Srinivas Pandruvada wrote:
> > When the current uncore frequency can't be read, don't create
> > attribute
> > "current_freq_khz" as any read will fail later. Some user space
> > applications like turbostat fail to continue with the failure. So,
> > check
> > error during attribute creation.
> >
> > Fixes: 414eef27283a ("platform/x86/intel/uncore-freq: Display
> > uncore current frequency")
> > Signed-off-by: Srinivas Pandruvada
> > <srinivas.pandruvada@linux.intel.com>
> > ---
> > Added fixes tag which added current_freq_khz. But after this
> > tag there is reorg of code, so need manual backport for some
> > versions.
> > I will separately submit to stable trees after merge.
>
> Can you for future updated patches please use the ususal [PATCH v2],
> [PATCH v3], etc. prefix ?
>
Sorry about this. I usually do with code change. But will keep in mind.
Thanks,
Srinivas
> Also please document the changes per version after the cutline, e.g.
> :
>
> ```
> ---
> Changes in v2:
> - Added fixes tag which added current_freq_khz. Note after this
> tag there is reorg of code, so need manual backport for some
> versions.
> I will separately submit to stable trees after merge.
> ```
>
> Regards,
>
> Hans
>
>
>
>
> >
> > .../x86/intel/uncore-frequency/uncore-frequency-common.c | 8
> > ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/platform/x86/intel/uncore-frequency/uncore-
> > frequency-common.c b/drivers/platform/x86/intel/uncore-
> > frequency/uncore-frequency-common.c
> > index 1152deaa0078..33ab207493e3 100644
> > --- a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-
> > common.c
> > +++ b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-
> > common.c
> > @@ -176,7 +176,7 @@ show_uncore_data(initial_max_freq_khz);
> >
> > static int create_attr_group(struct uncore_data *data, char *name)
> > {
> > - int ret, index = 0;
> > + int ret, freq, index = 0;
> >
> > init_attribute_rw(max_freq_khz);
> > init_attribute_rw(min_freq_khz);
> > @@ -197,7 +197,11 @@ static int create_attr_group(struct
> > uncore_data *data, char *name)
> > data->uncore_attrs[index++] = &data-
> > >min_freq_khz_dev_attr.attr;
> > data->uncore_attrs[index++] = &data-
> > >initial_min_freq_khz_dev_attr.attr;
> > data->uncore_attrs[index++] = &data-
> > >initial_max_freq_khz_dev_attr.attr;
> > - data->uncore_attrs[index++] = &data-
> > >current_freq_khz_dev_attr.attr;
> > +
> > + ret = uncore_read_freq(data, &freq);
> > + if (!ret)
> > + data->uncore_attrs[index++] = &data-
> > >current_freq_khz_dev_attr.attr;
> > +
> > data->uncore_attrs[index] = NULL;
> >
> > data->uncore_attr_group.name = name;
>
next prev parent reply other threads:[~2023-10-05 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 18:19 Srinivas Pandruvada
2023-10-05 7:03 ` Hans de Goede
2023-10-05 8:59 ` Andy Shevchenko
2023-10-05 14:07 ` srinivas pandruvada [this message]
2023-10-06 15:09 ` Ilpo Järvinen
2023-10-11 9:20 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 13:18 Srinivas Pandruvada
2023-10-03 13:10 ` Ilpo Järvinen
2023-10-03 15:13 ` srinivas pandruvada
2023-10-04 9:46 ` Ilpo Järvinen
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=5dda866185a286e61f949a48e04ff1ea6b3a5b03.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.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
Powered by JetHome