[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240627132230.hondzls5bt3jspay@desk>
Date: Thu, 27 Jun 2024 06:22:30 -0700
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Ricardo Neri <ricardo.neri-calderon@...ux.intel.com>
Cc: Dave Hansen <dave.hansen@...el.com>,
Brice Goglin <brice.goglin@...il.com>,
srinivas pandruvada <srinivas.pandruvada@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
daniel.sneddon@...ux.intel.com, tony.luck@...el.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-perf-users@...r.kernel.org,
Josh Poimboeuf <jpoimboe@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
"Liang, Kan" <kan.liang@...ux.intel.com>,
Andrew Cooper <andrew.cooper3@...rix.com>
Subject: Re: [PATCH 0/9] Add CPU-type to topology
On Thu, Jun 27, 2024 at 05:51:54AM -0700, Ricardo Neri wrote:
> ARM gives userspace specific details. This makes more sense to me. Instead
> of reading these details, user space would have to infer these details if
> a CPU type was given in sysfs.
>
> Having said that, Intel does have a CPUID leaf that gives the CPU type. Such
> leaf also has a "Native Model ID". Exposing only the CPU type may not be
> sufficient.
Do we know if there are applications that would benefit from this information?
We agreed to leave sysfs for another series. I will be sending v2 soon.
Powered by blists - more mailing lists