From: "Moger, Babu" <bmoger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
Babu Moger <babu.moger@amd.com>,
tony.luck@intel.com, bp@alien8.de
Cc: x86@kernel.org, Dave.Martin@arm.com, james.morse@arm.com,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
tglx@kernel.org, mingo@redhat.com, dave.hansen@linux.intel.com,
hpa@zytor.com, kas@kernel.org, rick.p.edgecombe@intel.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-coco@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [PATCH v3 2/3] fs/resctrl: Assign counters to existing groups when enabling mbm_event
Date: Wed, 7 Oct 2026 18:45:15 -0500 [thread overview]
Message-ID: <fca1c9b5-b895-48a2-8c01-84cd7668d10c@amd.com> (raw)
In-Reply-To: <a174730e-147e-4b7b-a8f8-e62f5709fef1@intel.com>
Hi Reinette,
On 10/7/2026 5:21 PM, Reinette Chatre wrote:
> Hi Babu,
>
> On 10/7/26 11:16 AM, Babu Moger wrote:
>> How about this?
>>
>> /*
>> * rdtgroup_assign_cntrs() - Assign counters to MBM events.
>> *
>> * Each group can accommodate two counters per domain: one for the total
>> * event and one for the local event. Assignments may fail due to the limited
>> * number of counters. However, it is not necessary to return failure.
>
> This drops the original motivation for why an error is not returned, leaving
> the claim that "it is not necessary" to return a failure without an explanation
> why.
>
> An example that adds a motivation:
>
> /*
> * rdtgroup_assign_cntrs() - Assign counters to enabled MBM events of a
> * resource group
> *
> * Each group can accommodate two counters per domain: one for the total
> * event and one for the local event. Assignments may fail due to the limited
> * number of counters.
> *
> * Intended to be called in auto assignment scenarios ("mbm_assign_on_mkdir"
> * enabled in "mbm_event" counter assignment mode) where counter assignment is
> * not required to succeed. Thus no failure is returned. Users can modify the
> * counter assignments afterwards if needed.
> */
>
Sounds good.
Thanks,
Babu
next prev parent reply other threads:[~2026-10-07 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:26 [PATCH v3 0/3] x86,fs/resctrl: Keep default MBM mode at boot and fix ABMC Babu Moger
2026-10-02 21:26 ` [PATCH v3 1/3] x86/resctrl: Fix ABMC counter programming Babu Moger
2026-10-06 17:47 ` Reinette Chatre
2026-10-07 16:33 ` Babu Moger
2026-10-02 21:26 ` [PATCH v3 2/3] fs/resctrl: Assign counters to existing groups when enabling mbm_event Babu Moger
2026-10-06 17:51 ` Reinette Chatre
2026-10-07 18:16 ` Babu Moger
2026-10-07 22:21 ` Reinette Chatre
2026-10-07 23:45 ` Moger, Babu [this message]
2026-10-02 21:26 ` [PATCH v3 3/3] x86,fs/resctrl: Keep mbm_assign_mode in default mode at boot Babu Moger
2026-10-06 17:53 ` Reinette Chatre
2026-10-07 18:54 ` Babu Moger
2026-10-07 22:21 ` Reinette Chatre
2026-10-07 23:47 ` Moger, Babu
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=fca1c9b5-b895-48a2-8c01-84cd7668d10c@amd.com \
--to=bmoger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.