Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Reinette Chatre <reinette.chatre@intel.com>
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 17:45:05 -0700	[thread overview]
Message-ID: <20260905004505.GAaptmEVxltONVfl2J@fat_crate.local> (raw)
In-Reply-To: <35ebb8d4-2ef0-4bc0-ac3f-afff0c95ae89@intel.com>

On Fri, Sep 04, 2026 at 02:15:08PM -0700, Reinette Chatre wrote:
> 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]. 

I would always ask myself how realistic is the use case. Here, I'm thinking
not that realistic unless you guys wanna support resctrl in a guest. Which
would be weird, IMHO, because a guest can fake all kinds of hw so controlling
resources of a fake hw is an exercise in futility.

So might as well answer that Sashiko review comment with "thanks, but no
thanks."

:-)

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette


  reply	other threads:[~2026-09-05  0:58 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
2026-09-05  0:45           ` Borislav Petkov [this message]
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=20260905004505.GAaptmEVxltONVfl2J@fat_crate.local \
    --to=bp@alien8.de \
    --cc=ben.horgan@arm.com \
    --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=reinette.chatre@intel.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