Linux Documentation
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ben Horgan <ben.horgan@arm.com>, <x86@kernel.org>,
	<james.morse@arm.com>, <fenghuay@nvidia.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <dave.hansen@linux.intel.com>,
	<hpa@zytor.com>, <corbet@lwn.net>, <linux-doc@vger.kernel.org>,
	<dave.martin@arm.com>
Subject: Re: [PATCH v5 0/3] x86,fs/resctrl,arm_mpam: Factor MBA parse-time conversion to be per-arch
Date: Fri, 4 Sep 2026 14:15:08 -0700	[thread overview]
Message-ID: <35ebb8d4-2ef0-4bc0-ac3f-afff0c95ae89@intel.com> (raw)
In-Reply-To: <20260904173615.GOapsBjyiT7uXHd-Qc@fat_crate.local>

Hi Boris,

On 9/4/26 10:36 AM, Borislav Petkov wrote:
> On Thu, Sep 03, 2026 at 08:37:51PM -0700, Borislav Petkov wrote:
>> Lemme have a look.
> 
> Sashiko has comments:
> 
> https://sashiko.dev/#/patchset/20260709093111.367851-1-ben.horgan%40arm.com
> 
> Please address them: if valid, fix them, if not, explain why they don't need
> to be fixed.
Sashiko has two comments. I'll defer to Ben on the first comment.

Sashiko's second comment is about resctrl's existing (not introduced by this patch)
Intel specific enumeration being resilient against a hypervisor misconfiguration.
Thus far resctrl assumed the enumeration would return what the actual hardware
is known to support.

Sashiko had similar "hypervisor misconfiguration" comments in response to another
resctrl series that already falls under the "cleanup" umbrella. It is not clear to
me how far resctrl needs to go to be resilient against hypervisor misconfiguration
but I can include needed validation addressing this report as part of [1]. 

Reinette

[1] https://sashiko.dev/#/patchset/cover.1788452481.git.reinette.chatre%40intel.com

  reply	other threads:[~2026-09-04 21:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  9:31 [PATCH v5 0/3] x86,fs/resctrl,arm_mpam: Factor MBA parse-time conversion to be per-arch Ben Horgan
2026-07-09  9:31 ` [PATCH v5 1/3] x86,fs/resctrl: Add resctrl_arch_preconvert_bw() Ben Horgan
2026-07-09  9:31 ` [PATCH v5 2/3] arm_mpam: resctrl: Add pass-through resctrl_arch_preconvert_bw() Ben Horgan
2026-07-09  9:31 ` [PATCH v5 3/3] fs/resctrl: Factor MBA parse-time conversion to be per-arch Ben Horgan
2026-07-14 17:45 ` [PATCH v5 0/3] x86,fs/resctrl,arm_mpam: " Reinette Chatre
2026-07-14 22:48   ` Moger, Babu
2026-07-14 23:59     ` Reinette Chatre
2026-09-03 15:40   ` Reinette Chatre
2026-09-04  3:37     ` Borislav Petkov
2026-09-04 17:36       ` Borislav Petkov
2026-09-04 21:15         ` Reinette Chatre [this message]
2026-09-05  0:45           ` Borislav Petkov
2026-07-15  0:13 ` Gavin Shan
2026-07-15 16:02   ` Reinette Chatre

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=35ebb8d4-2ef0-4bc0-ac3f-afff0c95ae89@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=ben.horgan@arm.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave.martin@arm.com \
    --cc=fenghuay@nvidia.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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