mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>, <bp@alien8.de>,
	<mingo@redhat.com>, <dave.hansen@linux.intel.com>,
	<hpa@zytor.com>, <dave.martin@arm.com>, <james.morse@arm.com>,
	<fenghuay@nvidia.com>, <babu.moger@amd.com>,
	<anil.keshavamurthy@broadcom.com>, <reinette.chatre@intel.com>,
	<tony.luck@intel.com>
Subject: Re: [PATCH v2 2/6] x86/resctrl: Parse ACPI CMRC table
Date: Fri, 5 Jun 2026 20:14:49 +0800	[thread overview]
Message-ID: <4887e68a-30f1-4914-a67d-e068aa4169ac@intel.com> (raw)
In-Reply-To: <87y0gu450q.ffs@fw13>

On 6/5/2026 12:57 AM, Thomas Gleixner wrote:
> On Fri, Jun 05 2026 at 00:11, Chen Yu wrote:
> 
>> The CMRC (Cache Monitoring Registers for CPU Agents Description)
>> sub-table of ERDT describes the MMIO registers used to read
>> cache monitoring counters (e.g. LLC occupancy) for an RMD.
>>
>> Parse each CMRC sub-table, ioremap its register window, and save
>> the CMRC pointer in the corresponding ERDT domain entry so that
>> later monitoring code can read the counters via MMIO.
>>
>> Suggested-by: Tony Luck <tony.luck@intel.com>
>> Signed-off-by: Chen Yu <yu.c.chen@intel.com>
>> ---
>>   arch/x86/kernel/cpu/resctrl/erdt.c | 40 ++++++++++++++++++++++++++++++
>>   1 file changed, 40 insertions(+)
>>
>> diff --git a/arch/x86/kernel/cpu/resctrl/erdt.c b/arch/x86/kernel/cpu/resctrl/erdt.c
>> index 3f309a4b15c8..d1eca4594f09 100644
>> --- a/arch/x86/kernel/cpu/resctrl/erdt.c
>> +++ b/arch/x86/kernel/cpu/resctrl/erdt.c
>> @@ -38,6 +38,7 @@ static bool erdt_available;
>>   static DEFINE_XARRAY(erdt_domain_xa); /* Indexed by L3 cache ID */
>>   
>>   #define ERDT_VALID_VERSION 1
>> +#define CMRC_VALID_INDEX_FUNC_VERSION 1
> 
> Please make this tabular so it's easy to parse
> 
> #define ERDT_VALID_VERSION			1
> #define CMRC_VALID_INDEX_FUNC_VERSION		1
> 

OK, fixed.

thanks,
Chenyu

  reply	other threads:[~2026-06-05 12:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 16:07 [PATCH v2 0/6] Introduce MMIO-based CMT access for Enhanced RDT Chen Yu
2026-06-04 16:08 ` [PATCH v2 1/6] x86/resctrl: Parse ACPI ERDT table and map RMDD domains by L3 cache ID Chen Yu
2026-06-04 16:56   ` Thomas Gleixner
2026-06-05 11:29     ` Chen, Yu C
2026-06-04 16:11 ` [PATCH v2 2/6] x86/resctrl: Parse ACPI CMRC table Chen Yu
2026-06-04 16:57   ` Thomas Gleixner
2026-06-05 12:14     ` Chen, Yu C [this message]
2026-06-04 16:11 ` [PATCH v2 3/6] x86/resctrl: Rename prev_msr to prev_mon_val Chen Yu
2026-06-04 16:11 ` [PATCH v2 4/6] x86/resctrl: Refactor the monitor read function Chen Yu
2026-06-04 16:11 ` [PATCH v2 5/6] fs/resctrl: Do not invoke smp_processor_id() in preemptible context Chen Yu
2026-06-04 16:11 ` [PATCH v2 6/6] x86/resctrl: Add support for L3 occupancy monitoring via RMID MMIO read Chen Yu

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=4887e68a-30f1-4914-a67d-e068aa4169ac@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=anil.keshavamurthy@broadcom.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave.martin@arm.com \
    --cc=fenghuay@nvidia.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=reinette.chatre@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --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

Powered by JetHome