mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Horgan <ben.horgan@arm.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
	tony.luck@intel.com, james.morse@arm.com, Dave.Martin@arm.com,
	babu.moger@amd.com, bp@alien8.de, tglx@linutronix.de,
	dave.hansen@linux.intel.com
Cc: x86@kernel.org, hpa@zytor.com, fustini@kernel.org,
	fenghuay@nvidia.com, peternewman@google.com,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH v2 14/14] fs/resctrl: Inform user space when status buffer overflowed
Date: Mon, 23 Mar 2026 10:49:42 +0000	[thread overview]
Message-ID: <a1a692bd-3e97-483a-aed0-8005a08534de@arm.com> (raw)
In-Reply-To: <0a2c56ac55725fe3131e214297649b9416671b9e.1774043709.git.reinette.chatre@intel.com>

Hi Reinette,

On 3/20/26 22:03, Reinette Chatre wrote:
> resctrl fs commands are becoming more powerful with, for example, a user
> able to use syntax like '*' to make broad configuration changes. Such
> commands that span multiple domains may result in more than one message
> printed to the last_cmd_status buffer with more planned.
> 
> Display "[truncated]" to user space when displaying the last_cmd_status
> buffer to communicate if it overflowed. Upon encountering this user space
> is expected to combine details about the failure found in info/last_cmd_status
> with related resctrl files to learn the accurate system state after the
> command failure.

LGTM:

Reviewed-by: Ben Horgan <ben.horgan@arm.com>

Thanks,

Ben


      reply	other threads:[~2026-03-23 10:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 22:03 [PATCH v2 00/14] x86,fs/resctrl: Improve resctrl quality and consistency Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 01/14] MAINTAINERS: Update resctrl entry Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 02/14] fs/resctrl: Add missing return value descriptions Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 03/14] fs/resctrl: Avoid "may be used uninitialized" warning Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 04/14] fs/resctrl: Use correct format specifier for printing error pointers Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 05/14] x86/resctrl: Protect against bad shift Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 06/14] fs/resctrl: Change pattern used to track number of entries in enum Reinette Chatre
2026-03-23 10:53   ` Ben Horgan
2026-03-20 22:03 ` [PATCH v2 07/14] fs/resctrl: Use accurate type for rdt_resource::rid Reinette Chatre
2026-03-23 10:54   ` Ben Horgan
2026-03-20 22:03 ` [PATCH v2 08/14] fs/resctrl: Pass error reading event through to user space Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 09/14] fs/resctrl: Add last_cmd_status support for writes to max_threshold_occupancy Reinette Chatre
2026-03-23  9:14   ` Chen, Yu C
2026-03-23 16:56     ` Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 10/14] fs/resctrl: Use accurate and symmetric exit flows Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 11/14] fs/resctrl: Use stricter checks on input to cpus/cpus_list file Reinette Chatre
2026-03-25 18:18   ` Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 12/14] fs/resctrl: Change last_cmd_status custom during input parsing Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 13/14] fs/resctrl: Communicate resource group deleted error via last_cmd_status Reinette Chatre
2026-03-20 22:03 ` [PATCH v2 14/14] fs/resctrl: Inform user space when status buffer overflowed Reinette Chatre
2026-03-23 10:49   ` Ben Horgan [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=a1a692bd-3e97-483a-aed0-8005a08534de@arm.com \
    --to=ben.horgan@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghuay@nvidia.com \
    --cc=fustini@kernel.org \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=peternewman@google.com \
    --cc=reinette.chatre@intel.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
all inboxes | Powered by JetHome®