From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] platform/x86: ISST: Support SST-TF revision 2
Date: Tue, 29 Apr 2025 10:29:44 -0700 [thread overview]
Message-ID: <07604feedc23ae2b404f8e9c0cfc1c19e2eb27e8.camel@linux.intel.com> (raw)
In-Reply-To: <f45da867-1090-51cc-b405-c4a639adb5ab@linux.intel.com>
On Tue, 2025-04-29 at 17:23 +0300, Ilpo Järvinen wrote:
> On Thu, 17 Apr 2025, Srinivas Pandruvada wrote:
>
> > SST-TF revision 2 supports a higher number of cores per bucket, as
> > the
> > current limit of 256 cores may be insufficient. To accommodate
> > this, a
> > new offset, "SST_TF_INFO-8," is introduced, allowing for a higher
> > core
> > count. Utilize this offset instead of the current "SST_TF_INFO-1"
> > offset,
> > based on SST-TF revision 2 or higher, and if there is a non-zero
> > core
> > count in any bucket.
> >
...
> > + if (feature_rev >= 2) {
> > + bool valid = false;
> > +
> > + for (i = 0; i < SST_TF_INFO_8_BUCKETS; ++i) {
> > + _read_tf_level_info("bucket_*_mod_count",
> > turbo_freq.bucket_core_counts[i],
> > + turbo_freq.level,
> > SST_TF_INFO_8_OFFSET,
> > + SST_TF_NUM_MOD_0_WIDTH
> > * i, SST_TF_NUM_MOD_0_WIDTH,
> > + SST_MUL_FACTOR_NONE)
> > +
> > + if (!valid &&
> > turbo_freq.bucket_core_counts[i])
>
> I'd just drop !valid from this check.
>
> > + valid = true;
> > + }
> > +
> > + if (valid)
>
>
> Should this be named instead to something like has_tf_info_8 ? (As
> this is
> not really valid/invalid check but whether this new info exists or
> not.)
We can.
Thanks,
Srinivas
>
> > + goto done_core_count;
> > + }
> > +
> > for (i = 0; i < TRL_MAX_BUCKETS; ++i)
> > _read_tf_level_info("bucket_*_core_count",
> > turbo_freq.bucket_core_counts[i],
> > turbo_freq.level,
> > SST_TF_INFO_1_OFFSET,
> > SST_TF_NUM_CORE_0_WIDTH * i,
> > SST_TF_NUM_CORE_0_WIDTH,
> > SST_MUL_FACTOR_NONE)
> >
> > +
> > +done_core_count:
> > +
> > if (copy_to_user(argp, &turbo_freq, sizeof(turbo_freq)))
> > return -EFAULT;
> >
> >
>
next prev parent reply other threads:[~2025-04-29 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 17:00 [PATCH 0/2] platform/x86: ISST: SST PP and TF " Srinivas Pandruvada
2025-04-17 17:00 ` [PATCH 1/2] platform/x86: ISST: Support SST-TF " Srinivas Pandruvada
2025-04-29 14:23 ` Ilpo Järvinen
2025-04-29 17:29 ` srinivas pandruvada [this message]
2025-04-17 17:00 ` [PATCH 2/2] platform/x86: ISST: Support SST-PP " Srinivas Pandruvada
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=07604feedc23ae2b404f8e9c0cfc1c19e2eb27e8.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®