X86 platform drivers
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Mario Limonciello" <mario.limonciello@amd.com>,
	"Perry Yuan" <perry.yuan@amd.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Huang Rui" <ray.huang@amd.com>,
	"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"open list:AMD HETERO CORE HARDWARE FEEDBACK DRIVER"
	<platform-driver-x86@vger.kernel.org>,
	"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	"open list:AMD PSTATE DRIVER" <linux-pm@vger.kernel.org>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: Re: [PATCH v9 01/13] Documentation: x86: Add AMD Hardware Feedback Interface documentation
Date: Mon, 28 Apr 2025 13:43:42 -0500	[thread overview]
Message-ID: <b2bf3ab3-38b6-4da3-a850-ff768139901d@kernel.org> (raw)
In-Reply-To: <aA_LZZRVnWdv6IdH@char.us.oracle.com>

On 4/28/2025 1:39 PM, Konrad Rzeszutek Wilk wrote:
> ..snip..
>> +Implementation details for Linux
>> +--------------------------------
>> +
>> +The implementation of threads scheduling consists of the following steps:
>> +
>> +1. A thread is spawned and scheduled to the ideal core using the default
>> +   heterogeneous scheduling policy.
>> +2. The processor profiles thread execution and assigns an enumerated
>> +   classification ID.
>> +   This classification is communicated to the OS via logical processor
>> +   scope MSR.
>> +3. During the thread context switch out the operating system consumes the
>> +   workload(WL) classification which resides in a logical processor scope MSR.
>> +4. The OS triggers the hardware to clear its history by writing to an MSR,
>> +   after consuming the WL classification and before switching in the new thread.
>> +5. If due to the classification, ranking table, and processor availability,
>> +   the thread is not on its ideal processor, the OS will then consider
>> +   scheduling the thread on its ideal processor (if available).
> 
> Can you expand on 5) please?  The one patch in this patchset that
> touches the process file just does an WRMSR.

Hi, thanks for looking.

This scheduler change is not first part of the series and is going to be 
a follow up series.

I left it in the documentation as it explains the intended implementation.

  reply	other threads:[~2025-04-28 18:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23  1:46 [PATCH v9 00/13] Add support for AMD hardware feedback interface Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 01/13] Documentation: x86: Add AMD Hardware Feedback Interface documentation Mario Limonciello
2025-04-28 18:39   ` Konrad Rzeszutek Wilk
2025-04-28 18:43     ` Mario Limonciello [this message]
2025-04-23  1:46 ` [PATCH v9 02/13] MAINTAINERS: Add maintainer entry for AMD Hardware Feedback Driver Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 03/13] x86/msr-index: define AMD heterogeneous CPU related MSR Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 04/13] platform/x86: hfi: Introduce AMD Hardware Feedback Interface Driver Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 05/13] platform/x86: hfi: parse CPU core ranking data from shared memory Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 06/13] platform/x86: hfi: init per-cpu scores for each class Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 07/13] platform/x86: hfi: add online and offline callback support Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 08/13] platform/x86: hfi: add power management callback Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 09/13] x86/process: Clear hardware feedback history for AMD processors Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 10/13] cpufreq/amd-pstate: Disable preferred cores on designs with workload classification Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 11/13] platform/x86/amd: hfi: Set ITMT priority from ranking data Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 12/13] platform/x86/amd: hfi: Add debugfs support Mario Limonciello
2025-04-23  1:46 ` [PATCH v9 13/13] x86/itmt: Add debugfs file to show core priorities Mario Limonciello

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=b2bf3ab3-38b6-4da3-a850-ff768139901d@kernel.org \
    --to=superm1@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=gautham.shenoy@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=hpa@zytor.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mingo@redhat.com \
    --cc=perry.yuan@amd.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@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