[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZwndFfdpevdwxurj@archie.me>
Date: Sat, 12 Oct 2024 09:21:09 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Mario Limonciello <mario.limonciello@....com>,
Borislav Petkov <bp@...en8.de>, Hans de Goede <hdegoede@...hat.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: x86@...nel.org, "Gautham R . Shenoy" <gautham.shenoy@....com>,
Perry Yuan <perry.yuan@....com>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-pm@...r.kernel.org,
platform-driver-x86@...r.kernel.org,
Shyam Sundar S K <Shyam-sundar.S-k@....com>
Subject: Re: [PATCH v2 00/13] Add support for AMD hardware feedback interface
On Thu, Oct 10, 2024 at 08:29:47PM -0500, Mario Limonciello wrote:
> On 10/10/2024 19:54, Bagas Sanjaya wrote:
> > On Thu, Oct 10, 2024 at 02:36:52PM -0500, Mario Limonciello wrote:
> > > The AMD Heterogeneous core design and Hardware Feedback Interface (HFI)
> > > provide behavioral classification and a dynamically updated ranking table
> > > for the scheduler to use when choosing cores for tasks.
> > >
> > > Threads are classified during runtime into enumerated classes.
> > > Currently, the driver supports 3 classes (0 through 2). These classes
> > > represent thread performance/power characteristics that may benefit from
> > > special scheduling behaviors. The real-time thread classification is
> > > consumed by the operating system and is used to inform the scheduler of
> > > where the thread should be placed for optimal performance or energy efficiency.
> > >
> > > The thread classification helps to select CPU from a ranking table that describes
> > > an efficiency and performance ranking for each classification from two dimensions.
> > >
> > > The ranking data provided by the ranking table are numbers ranging from 0 to 255,
> > > where a higher performance value indicates higher performance capability and a higher
> > > efficiency value indicates greater efficiency. All the CPU cores are ranked into
> > > different class IDs. Within each class ranking, the cores may have different ranking
> > > values. Therefore, picking from each classification ID will later allow the scheduler
> > > to select the best core while threads are classified into the specified workload class.
> > >
> > > This series was originally submitted by Perry Yuan [1] but he is now doing a different
> > > role and he asked me to take over.
> >
> > Sorry but can you specify the base commit/tree of this series? I can't apply
> > it on top of current platform-drivers-x86.git, though.
> >
> > Confused...
> >
>
> Sorry about that. As it crosses a few subsystems it will require some
> coordination to properly land once it has review comments.
>
> It's (currently) based off:
> https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/log/?h=linux-next
>
> commit 57533bc760ae ("cpufreq/amd-pstate: Fix non kerneldoc comment")
Series successfully applied for review, thanks!
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists