From: Babu Moger <babu.moger@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Moger, Babu" <bmoger@amd.com>,
Reinette Chatre <reinette.chatre@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"Dave.Martin@arm.com" <Dave.Martin@arm.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"tglx@kernel.org" <tglx@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"Eranian, Stephane" <eranian@google.com>,
"peternewman@google.com" <peternewman@google.com>
Subject: Re: [PATCH 1/2] x86/resctrl, Documentation: Keep mbm_assign_mode "default" on boot
Date: Thu, 30 Jul 2026 14:49:05 -0500 [thread overview]
Message-ID: <d364100d-45e4-458e-97d5-05416fbe5bef@amd.com> (raw)
In-Reply-To: <20260730194328.GEamupYLsURg6VvxBU@fat_crate.local>
On 7/30/26 14:43, Borislav Petkov wrote:
> On Thu, Jul 30, 2026 at 02:39:40PM -0500, Babu Moger wrote:
>> Therefore, creating more than 64 monitoring groups in the default
>> measurement mode can lead to inaccurate measurement results.
>
> I have this there now:
>
> In either case, creating more monitoring groups than available counters can
> lead to innacuracies during measurement.
>
That is correct.
Thanks
Babu
next prev parent reply other threads:[~2026-07-30 19:49 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 21:13 [PATCH 1/2] x86/resctrl, Documentation: Keep mbm_assign_mode "default" on boot Babu Moger
2026-07-17 21:13 ` [PATCH 2/2] x86/resctrl: Fix ABMC counter programming for extended counter ranges Babu Moger
2026-07-17 22:56 ` [PATCH 1/2] x86/resctrl, Documentation: Keep mbm_assign_mode "default" on boot Reinette Chatre
2026-07-20 17:00 ` Babu Moger
2026-07-20 18:27 ` Reinette Chatre
2026-07-20 19:15 ` Babu Moger
2026-07-21 20:54 ` Reinette Chatre
2026-07-23 18:03 ` Babu Moger
2026-07-23 21:46 ` Reinette Chatre
2026-07-24 20:57 ` Moger, Babu
2026-07-24 22:28 ` Reinette Chatre
2026-07-24 23:12 ` Borislav Petkov
2026-07-24 23:53 ` Reinette Chatre
2026-07-27 14:05 ` Borislav Petkov
2026-07-27 15:25 ` Reinette Chatre
2026-07-27 17:24 ` Babu Moger
2026-07-27 18:12 ` Reinette Chatre
2026-07-27 20:17 ` Babu Moger
2026-07-27 21:42 ` Reinette Chatre
2026-07-27 22:44 ` Moger, Babu
2026-07-27 23:29 ` Moger, Babu
2026-07-28 0:29 ` Reinette Chatre
2026-07-28 17:04 ` Borislav Petkov
2026-07-28 17:25 ` Babu Moger
2026-07-20 20:12 ` Babu Moger
2026-07-28 19:18 ` Borislav Petkov
2026-07-28 19:46 ` Babu Moger
2026-07-28 19:58 ` Luck, Tony
2026-07-28 20:18 ` Babu Moger
2026-07-28 20:24 ` Luck, Tony
2026-07-28 20:43 ` Babu Moger
2026-07-28 21:58 ` Reinette Chatre
2026-07-28 22:20 ` Moger, Babu
2026-07-30 18:46 ` Borislav Petkov
2026-07-30 19:39 ` Babu Moger
2026-07-30 19:43 ` Borislav Petkov
2026-07-30 19:49 ` Babu Moger [this message]
2026-07-30 20:40 ` Luck, Tony
2026-07-30 20:59 ` Babu Moger
2026-07-31 0:34 ` Borislav Petkov
2026-07-31 14:59 ` Reinette Chatre
[not found] ` <20260801012227.GEam1KUyMz601QOzrT@fat_crate.local>
2026-08-01 23:47 ` Reinette Chatre
2026-08-04 19:16 ` Borislav Petkov
2026-08-04 22:10 ` Reinette Chatre
[not found] ` <20260804224703.GFanJr52UbKBrCOTij@fat_crate.local>
2026-08-04 23:05 ` Luck, Tony
2026-08-04 23:40 ` Borislav Petkov
2026-08-05 0:02 ` Luck, Tony
2026-08-05 0:21 ` Borislav Petkov
2026-08-04 23:35 ` Reinette Chatre
2026-08-05 0:12 ` Reinette Chatre
2026-08-05 22:40 ` Moger, Babu
2026-08-04 23:44 ` Moger, Babu
2026-08-05 5:03 ` Reinette Chatre
2026-07-31 15:34 ` Luck, Tony
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=d364100d-45e4-458e-97d5-05416fbe5bef@amd.com \
--to=babu.moger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=bmoger@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.com \
--cc=skhan@linuxfoundation.org \
--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