mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>, Perry Yuan <perry.yuan@amd.com>
Cc: gautham.shenoy@amd.com, rafael.j.wysocki@intel.com,
	viresh.kumar@linaro.org, Ray.Huang@amd.com,
	Alexander.Deucher@amd.com, Xinmei.Huang@amd.com,
	Xiaojian.Du@amd.com, Li.Meng@amd.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 08/10] x86/cpufeatures: Add feature bits for AMD heterogeneous processor
Date: Tue, 11 Jun 2024 09:31:54 -0500	[thread overview]
Message-ID: <e41fd460-6b50-4792-9328-3eda370672e4@amd.com> (raw)
In-Reply-To: <20240611105216.GAZmgsYC-J_yLfdupF@fat_crate.local>

On 6/11/2024 05:52, Borislav Petkov wrote:
> On Tue, Jun 11, 2024 at 04:52:24PM +0800, Perry Yuan wrote:
>> Subject: Re: [PATCH v3 08/10] x86/cpufeatures: Add feature bits for AMD heterogeneous processor
> 
> "... Add a heterogeneous core topology feature bit"
> 
> not "feature bits"
> 
>> CPUID leaf 0x80000026 advertises core types with different efficiency rankings
>>
>> Bit 30 indicates the heterogeneous core topology feature, if the bit
>> set, it means not all instances at the current hierarchical level have
>> the same core topology.
>>
>> For better utilization of feature words and help to identify core type,
>> X86_FEATURE_HETERO_CORE_TOPOLOGY is added as a few scattered feature bits.
> 
> This sentence is not needed.
> 
>> PDF p274
>>
>> Link: https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/programmer-references/24593.pdf
> 
> This link will become obsolete, you can say instead
> 
> Search the web for "architecture programmer's manual volume 2 system
> programming docID #25493" in order to find the official document.
> 

Another option is to upload it a non ephemeral location like a kernel 
Bugzilla and link to that.  I do recall there is a bug already opened 
for this purpose in the past.

  reply	other threads:[~2024-06-11 14:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  8:52 [PATCH v3 00/10] AMD Pstate Driver Fixes and Improvements Perry Yuan
2024-06-11  8:52 ` [PATCH v3 01/10] cpufreq: amd-pstate: optimize the initial frequency values verification Perry Yuan
2024-06-11 18:50   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 02/10] cpufreq: amd-pstate: remove unused variable nominal_freq Perry Yuan
2024-06-11 18:50   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 03/10] cpufreq: amd-pstate: show CPPC debug message if CPPC is not supported Perry Yuan
2024-06-11 18:50   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 04/10] cpufreq: amd-pstate: add debug message while CPPC is supported and disabled by SBIOS Perry Yuan
2024-06-11 19:00   ` Mario Limonciello
2024-06-12  8:04   ` Gautham R.Shenoy
2024-06-11  8:52 ` [PATCH v3 05/10] Documentation: PM: amd-pstate: add debugging section for driver loading failure Perry Yuan
2024-06-11 19:06   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 06/10] Documentation: PM: amd-pstate: add guided mode to the Operation mode Perry Yuan
2024-06-12  8:12   ` Gautham R.Shenoy
2024-06-11  8:52 ` [PATCH v3 07/10] cpufreq: amd-pstate: switch boot_cpu_has() to cpu_feature_enabled() Perry Yuan
2024-06-12  8:14   ` Gautham R.Shenoy
2024-06-11  8:52 ` [PATCH v3 08/10] x86/cpufeatures: Add feature bits for AMD heterogeneous processor Perry Yuan
2024-06-11 10:52   ` Borislav Petkov
2024-06-11 14:31     ` Mario Limonciello [this message]
2024-06-11 14:39       ` Borislav Petkov
2024-06-13  8:59         ` Yuan, Perry
2024-06-13  9:35           ` Borislav Petkov
2024-06-11  8:52 ` [PATCH v3 09/10] cpufreq: amd-pstate: implement heterogeneous core topology for highest performance initialization Perry Yuan
2024-06-11 19:29   ` Mario Limonciello
2024-06-13  7:13   ` Gautham R.Shenoy
2024-06-13  8:25     ` Yuan, Perry
2024-06-11  8:52 ` [PATCH v3 10/10] cpufreq: amd-pstate: automatically load pstate driver by default Perry Yuan
2024-06-11 19:35   ` Mario Limonciello
2024-06-13  8:19   ` Gautham R.Shenoy
2024-06-13  8:44     ` Yuan, Perry

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=e41fd460-6b50-4792-9328-3eda370672e4@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Li.Meng@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Xiaojian.Du@amd.com \
    --cc=Xinmei.Huang@amd.com \
    --cc=bp@alien8.de \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=perry.yuan@amd.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=viresh.kumar@linaro.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