[lkml]   [2019]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 08/11] powercap/intel_rapl: Support multi-die/package
On Thu, Feb 21, 2019 at 12:44 AM Len Brown <> wrote:
> On Wed, Feb 20, 2019 at 6:02 AM Peter Zijlstra <> wrote:
> > > list_for_each_entry(rp, &rapl_packages, plist) {
> > > @@ -1457,7 +1457,7 @@ static void rapl_remove_package(struct rapl_package *rp)
> > > /* called from CPU hotplug notifier, hotplug lock held */
> > > static struct rapl_package *rapl_add_package(int cpu)
> > > {
> > > - int id = topology_physical_package_id(cpu);
> > > + int id = topology_unique_die_id(cpu);
> > > struct rapl_package *rp;
> > > int ret;
> >
> > And now your new function names are misnomers.
> That is fair.
> Seems that a subsequent re-name-only patch is appropriate.

I'm not sure that re-naming these functions is a good idea.

Fundamentally, the reason stems from the SDM being in-consistent.
And the reason that the SDM is inconsistent is for compatibility.

ie. the PACKAGE MSRs in the SDM are still called PACKAGE MSRs,
even though on a multi-die system, they are DIE scoped.
There is no plan to re-name all of those MSRs.

And so what do you call a routine that parses a PACKAGE_RAPL domain?
Well, it is still called PACKAGE MSR, even though the code is smart enough
to know that on a multi-die system, its scope is die-scoped, not package-scoped.

And yes, just to confuse things, there WILL be PACKAGE scope MSRs
in the future that span multiple die on multi-die systems. No, it will not
be a surprise when they appear -- by definition, they will be different
and incompatible with previous PACKAGE MSRs. We will need to update
some software to be smart about handling them -- no blind assumptions
on using the word "package" in this context.

So unless Rui disagrees, I'm inclined to leave these routine names alone.

Len Brown, Intel Open Source Technology Center

 \ /
  Last update: 2019-02-26 05:43    [W:0.094 / U:2.712 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site