From: Shakeel Butt <shakeel.butt@linux.dev>
To: Peter Newman <peternewman@google.com>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
Tony Luck <tony.luck@intel.com>,
Dave Martin <Dave.Martin@arm.com>,
James Morse <james.morse@arm.com>,
Babu Moger <babu.moger@amd.com>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Meta kernel team <kernel-team@meta.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] x86,resctrl: Read event counters with an IPI when the read cannot block
Date: Mon, 26 Oct 2026 20:17:40 -0700 [thread overview]
Message-ID: <auAXqinfh5lTBCVQ@linux.dev> (raw)
In-Reply-To: <CALPaoCi2YV0EHTjz0Q8c0PE_CGXPcupqfGd7=YfK8UqpLzn1oA@mail.gmail.com>
On Thu, Oct 22, 2026 at 11:05:42AM +0200, Peter Newman wrote:
> On Thu, Oct 22, 2026 at 12:58 AM Reinette Chatre
> <reinette.chatre@intel.com> wrote:
> >
> >
> > If the goal is indeed to obtain accurate monitoring data at regular
> > intervals when using the stated hardware at its full capacity then
> > I would suggest that you consider the per-group rate files that Peter
> > settled on per
> > https://lore.kernel.org/all/CALPaoCgpnVORZfbKVLXDFUZvv8jhpShHPzB3cwdLTZQH1o9ULw@mail.gmail.com/
> >
> > I actually cannot remember seeing an update on that work after he posted that
> > message and my assumption has been that that is what they have been using since
> > then.
>
> These changes have been available within Google for a while, but I
> don't believe they've ever gone into use. They've had a lot of other
> issues with the MBM implementations on AMD and have been estimating
> jobs' bandwidth using the offcore PMU instead.
>
> Shakeel, I can share the changes for you to try out, but they won't be
> up to the standard for code review. If it works for you, that would be
> one confirmed user and I could put more time into it.
Yes please, do share, I will take a look.
next prev parent reply other threads:[~2026-10-27 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:13 Shakeel Butt
2026-10-21 22:58 ` Reinette Chatre
2026-10-22 9:05 ` Peter Newman
2026-10-27 3:17 ` Shakeel Butt [this message]
2026-10-27 3:15 ` Shakeel Butt
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=auAXqinfh5lTBCVQ@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peternewman@google.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
all inboxes | Powered by JetHome®