From: "Moger, Babu" <bmoger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
Babu Moger <babu.moger@amd.com>,
corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de
Cc: fenghua.yu@intel.com, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, paulmck@kernel.org,
akpm@linux-foundation.org, quic_neeraju@quicinc.com,
rdunlap@infradead.org, damien.lemoal@opensource.wdc.com,
songmuchun@bytedance.com, peterz@infradead.org,
jpoimboe@kernel.org, pbonzini@redhat.com,
chang.seok.bae@intel.com, pawan.kumar.gupta@linux.intel.com,
jmattson@google.com, daniel.sneddon@linux.intel.com,
sandipan.das@amd.com, tony.luck@intel.com, james.morse@arm.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bagasdotme@gmail.com, eranian@google.com,
christophe.leroy@csgroup.eu, jarkko@kernel.org,
adrian.hunter@intel.com, quic_jiles@quicinc.com,
peternewman@google.com
Subject: Re: [PATCH v12 10/10] x86/resctrl: Display RMID of resource group
Date: Thu, 12 Oct 2023 17:06:27 -0500 [thread overview]
Message-ID: <5eade0a5-89d6-e93a-f5f0-e404fb37e2c4@amd.com> (raw)
In-Reply-To: <c030c50a-201b-4a73-b3d6-b9b298f1b251@intel.com>
Hi Reinette,
On 10/12/2023 11:02 AM, Reinette Chatre wrote:
> Hi Babu,
>
> On 10/10/2023 4:33 PM, Babu Moger wrote:
>> In x86, hardware uses RMID to identify a monitoring group. When a user
>> creates a monitor group these details are not visible. These details
>> can help resctrl debugging.
>>
>> Add RMID(mon_hw_id) to the monitor groups display in resctrl interface.
>> Users can see these details when resctrl is mounted with "-o debug" option.
>>
>> Add RFTYPE_MON_BASE complements existing RFTYPE_CTRL_BASE and represents
>> files belonging to monitoring groups.
> "Add RFTYPE_MON_BASE complements ... " -> "Add RFTYPE_MON_BASE that complements ..."?
Sure. Thanks
Babu
prev parent reply other threads:[~2023-10-12 22:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 23:33 [PATCH v12 00/10] x86/resctrl: Miscellaneous resctrl features Babu Moger
2023-10-10 23:33 ` [PATCH v12 01/10] x86/resctrl: Add multiple tasks to the resctrl group at once Babu Moger
2023-10-10 23:33 ` [PATCH v12 02/10] x86/resctrl: Simplify rftype flag definitions Babu Moger
2023-10-10 23:33 ` [PATCH v12 03/10] x86/resctrl: Rename rftype flags for consistency Babu Moger
2023-10-10 23:33 ` [PATCH v12 04/10] x86/resctrl: Add comments on RFTYPE flags hierarchy Babu Moger
2023-10-11 0:56 ` Reinette Chatre
2023-10-11 16:57 ` Moger, Babu
2023-10-12 16:01 ` Reinette Chatre
2023-10-12 18:28 ` Moger, Babu
2023-10-10 23:33 ` [PATCH v12 05/10] x86/resctrl: Unwind the errors inside rdt_enable_ctx() Babu Moger
2023-10-10 23:33 ` [PATCH v12 06/10] x86/resctrl: Move default group file creation to mount Babu Moger
2023-10-10 23:33 ` [PATCH v12 07/10] x86/resctrl: Introduce "-o debug" mount option Babu Moger
2023-10-10 23:33 ` [PATCH v12 08/10] x86/resctrl: Display CLOSID for resource group Babu Moger
2023-10-10 23:33 ` [PATCH v12 09/10] x86/resctrl: Add support for the files for MON groups only Babu Moger
2023-10-12 16:02 ` Reinette Chatre
2023-10-12 18:29 ` Moger, Babu
2023-10-10 23:33 ` [PATCH v12 10/10] x86/resctrl: Display RMID of resource group Babu Moger
2023-10-12 16:02 ` Reinette Chatre
2023-10-12 22:06 ` Moger, Babu [this message]
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=5eade0a5-89d6-e93a-f5f0-e404fb37e2c4@amd.com \
--to=bmoger@amd.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=babu.moger@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jarkko@kernel.org \
--cc=jmattson@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peternewman@google.com \
--cc=peterz@infradead.org \
--cc=quic_jiles@quicinc.com \
--cc=quic_neeraju@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=sandipan.das@amd.com \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--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