public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Borislav Petkov" <bp@alien8.de>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	x86@kernel.org, "Gautham R . Shenoy" <gautham.shenoy@amd.com>,
	"Perry Yuan" <perry.yuan@amd.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-pm@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH v2 05/13] platform/x86: hfi: Introduce AMD Hardware Feedback Interface Driver
Date: Thu, 17 Oct 2024 16:33:43 -0700	[thread overview]
Message-ID: <20241017233343.GA308@ranerica-svr.sc.intel.com> (raw)
In-Reply-To: <1395bee1-95a7-4d14-a5e8-0e1dc71fadac@amd.com>

On Tue, Oct 15, 2024 at 01:09:42PM -0500, Mario Limonciello wrote:
> > 
> > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=206537
> > 
> > I tried to find the HFI details on the documents in this "bug" but I could
> > not find them. What document in specific could I look at?
> > 
> > Thanks and BR,
> > Ricardo
> 
> Hi Ricardo,
> 
> It is spread out across multiple places.  This is part of the reason for
> patch 1 in the series outlines details of how it works.
> 
> The reason for that "collect all" Bugzilla for documentation is because the
> URLs for AMD documentation have undergone changes in the past and it makes
> it difficult to put stable URLs in commit messages.  So teams that want to
> reference documentation put it on a dump all bug for a stable URL to
> reference.
> 
> On that link you will find the APM, which will have some documentation
> specifically for the CPUID leafs used for topology identification and
> clearing history.
> 
> Read patch 1 and let me know if it covers what specifically you're looking
> for.  If it's still missing some info let me know what you would like added.

Thank you for your reply! I read patch 1. I was wondering specifically about
more details of the Class ID. I see that they have associated counters and
desired scheduling behavior.

I was also curious about the layout of the HFI table. I guess I can infer it
from patches 5 and 6 but if there is a picture already, I wouldn't mind. ;)


  reply	other threads:[~2024-10-17 23:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 19:36 [PATCH v2 00/13] Add support for AMD hardware feedback interface Mario Limonciello
2024-10-10 19:36 ` [PATCH v2 01/13] Documentation: x86: Add AMD Hardware Feedback Interface documentation Mario Limonciello
2024-10-12  3:53   ` Bagas Sanjaya
2024-10-10 19:36 ` [PATCH v2 02/13] MAINTAINERS: Add maintainer entry for AMD Hardware Feedback Driver Mario Limonciello
2024-10-10 19:36 ` [PATCH v2 03/13] x86/cpufeatures: add X86_FEATURE_WORKLOAD_CLASS feature bit Mario Limonciello
2024-10-10 19:36 ` [PATCH v2 04/13] x86/msr-index: define AMD heterogeneous CPU related MSR Mario Limonciello
2024-10-10 19:36 ` [PATCH v2 05/13] platform/x86: hfi: Introduce AMD Hardware Feedback Interface Driver Mario Limonciello
2024-10-14  9:10   ` Ilpo Järvinen
2024-10-14 19:46     ` Mario Limonciello
2024-10-14  9:20   ` Ilpo Järvinen
2024-10-15  3:52   ` Ricardo Neri
2024-10-15 18:09     ` Mario Limonciello
2024-10-17 23:33       ` Ricardo Neri [this message]
2024-10-18 13:46         ` Mario Limonciello
2024-10-16  9:36   ` Uwe Kleine-König
2024-10-16  9:59     ` Hans de Goede
2024-10-16 16:06       ` Mario Limonciello
2024-10-10 19:36 ` [PATCH v2 06/13] platform/x86: hfi: parse CPU core ranking data from shared memory Mario Limonciello
2024-10-14 10:14   ` Ilpo Järvinen
2024-10-14 20:09     ` Mario Limonciello
2024-10-10 19:36 ` [PATCH v2 07/13] platform/x86: hfi: init per-cpu scores for each class Mario Limonciello
2024-10-14 10:15   ` Ilpo Järvinen
2024-10-10 19:37 ` [PATCH v2 08/13] platform/x86: hfi: add online and offline callback support Mario Limonciello
2024-10-14 10:27   ` Ilpo Järvinen
2024-10-10 19:37 ` [PATCH v2 09/13] platform/x86: hfi: add power management callback Mario Limonciello
2024-10-14 10:29   ` Ilpo Järvinen
2024-10-10 19:37 ` [PATCH v2 10/13] x86/cpu: Enable SD_ASYM_PACKING for DIE Domain on AMD Processors Mario Limonciello
2024-10-10 19:37 ` [PATCH v2 11/13] x86/process: Clear hardware feedback history for AMD processors Mario Limonciello
2024-10-10 19:37 ` [PATCH v2 12/13] cpufreq/amd-pstate: Disable preferred cores on designs with workload classification Mario Limonciello
2024-10-10 19:37 ` [PATCH v2 13/13] platform/x86/amd: hfi: Set ITMT priority from ranking data Mario Limonciello
2024-10-11  0:54 ` [PATCH v2 00/13] Add support for AMD hardware feedback interface Bagas Sanjaya
2024-10-11  1:29   ` Mario Limonciello
2024-10-12  2:21     ` Bagas Sanjaya

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=20241017233343.GA308@ranerica-svr.sc.intel.com \
    --to=ricardo.neri-calderon@linux.intel.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=bp@alien8.de \
    --cc=gautham.shenoy@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.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=perry.yuan@amd.com \
    --cc=platform-driver-x86@vger.kernel.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