From: Ben Horgan <ben.horgan@arm.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
linux-kernel@vger.kernel.org
Cc: tony.luck@intel.com, Dave.Martin@arm.com, james.morse@arm.com,
babu.moger@amd.com, bp@alien8.de
Subject: Re: [PATCH v1] fs/resctrl: Add missing kconfig entry for CONFIG_RESCTRL_ASSIGN_FIXED
Date: Thu, 15 Jan 2026 15:46:27 +0000 [thread overview]
Message-ID: <050fcf3b-d390-4692-b944-2d59a71888e4@arm.com> (raw)
In-Reply-To: <de29108c-f0f8-45c5-8f33-52b3da79d75a@intel.com>
Hi Reinette,
On 1/15/26 15:37, Reinette Chatre wrote:
> Hi Ben,
>
> On 1/15/26 2:32 AM, Ben Horgan wrote:
>> On 1/14/26 19:09, Reinette Chatre wrote:
>>> On 1/13/26 6:49 AM, Ben Horgan wrote:
>>>> The commit 3b497c3f4f04 ("fs/resctrl: Introduce the interface to display
>>>> monitoring modes") introduced CONFIG_RESCTRL_ASSIGN_FIXED but did not add
>>>> the kconfig entry. Add this.
>>>>
>>>> Also, take the opportunity ensure that any user attempt to change the
>>>> assign mode fails from the resctrl code rather than delegating to the arch
>>>> specific code and let the user know by adding a message in last_cmd_status.
>>>
>>> Why *any* attempt? Avoiding delegating to arch seems ok as a goal but this change
>>> additionally changes interface with user space. Current behavior when user writes
>>> existing mode to the file is to just return success. For example, if current mode
>>> is "default" and user writes "default". This patch changes this behavior to fail
>>> instead. Is this intended?
>>
>> Intended but as you point out, it would be best to accept the current
>> value without error for maximum compatibility between architectures.
>> I'll update the config option help text to reflect this. Was the help
>> text also discussed previously?
>
> It is not clear to me which help text you are referring to. Could you
> please point me to it?
I just mean the description in Kconfig. Maybe I'm using the wrong
terminology?
From this patch:
help
Enabled by the architecture when the counter assignment mode is not
configurable. This ensures that counter assignment is not
advertised as
configurable and configuration attempts fail.
>
> Reinette
Thanks,
Ben
next prev parent reply other threads:[~2026-01-15 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 14:49 Ben Horgan
2026-01-13 19:10 ` Babu Moger
2026-01-15 11:41 ` Ben Horgan
2026-01-14 19:09 ` Reinette Chatre
2026-01-15 10:32 ` Ben Horgan
2026-01-15 15:37 ` Reinette Chatre
2026-01-15 15:46 ` Ben Horgan [this message]
2026-01-15 17:19 ` Reinette Chatre
2026-01-16 9:51 ` Ben Horgan
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=050fcf3b-d390-4692-b944-2d59a71888e4@arm.com \
--to=ben.horgan@arm.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@intel.com \
/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®