From: Borislav Petkov <bp@alien8.de>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tony.luck@intel.com, james.morse@arm.com, Dave.Martin@arm.com,
babu.moger@amd.com, tglx@linutronix.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
ben.horgan@arm.com, fustini@kernel.org, fenghuay@nvidia.com,
peternewman@google.com, yu.c.chen@intel.com,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH v5 02/10] x86/resctrl: Protect against bad shift
Date: Wed, 22 Jul 2026 13:03:11 -0700 [thread overview]
Message-ID: <20260722200311.GFamEh_2Z6p3MrXpVr@fat_crate.local> (raw)
In-Reply-To: <ae04714b-566e-4b21-ba6c-2f42c6400e87@intel.com>
On Wed, Jul 22, 2026 at 08:59:39AM -0700, Reinette Chatre wrote:
> I am trying to help with bigger things in resctrl and find it easier to do so when
> working on a baseline that is without implicit assumptions.
Ofc.
> I plan to use changelog below that aims to address the items you highlighted and also
> changed the math to make the bandwidth boundary where resctrl stop working clear:
LGTM.
You can send me an updated patch now and I can integrate it into the pile.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-07-22 20:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 4:27 [PATCH v5 00/10] x86,fs/resctrl: Improve resctrl quality and consistency Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 01/10] fs/resctrl: Use correct format specifier for printing error pointers Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 02/10] x86/resctrl: Protect against bad shift Reinette Chatre
2026-07-21 1:59 ` Borislav Petkov
2026-07-21 16:14 ` Reinette Chatre
2026-07-21 23:15 ` Borislav Petkov
2026-07-21 23:50 ` Reinette Chatre
2026-07-22 0:50 ` Borislav Petkov
2026-07-22 15:59 ` Reinette Chatre
2026-07-22 20:03 ` Borislav Petkov [this message]
2026-07-22 21:07 ` Reinette Chatre
2026-07-22 21:11 ` [PATCH v5.1 " Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 03/10] fs/resctrl: Change pattern used to track number of entries in enum Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 04/10] fs/resctrl: Use accurate type for rdt_resource::rid Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 05/10] fs/resctrl: Pass error reading event through to user space Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 06/10] fs/resctrl: Use accurate and symmetric exit flows Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 07/10] fs/resctrl: Change last_cmd_status custom during input parsing Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 08/10] fs/resctrl: Add last_cmd_status support for writes to max_threshold_occupancy Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 09/10] fs/resctrl: Communicate resource group deleted error via last_cmd_status Reinette Chatre
2026-07-01 4:27 ` [PATCH v5 10/10] fs/resctrl: Inform user space when status buffer overflowed Reinette Chatre
2026-07-14 17:49 ` [PATCH v5 00/10] x86,fs/resctrl: Improve resctrl quality and consistency Reinette Chatre
2026-07-20 17:16 ` Borislav Petkov
2026-07-14 22:45 ` Moger, Babu
2026-07-15 0:00 ` 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=20260722200311.GFamEh_2Z6p3MrXpVr@fat_crate.local \
--to=bp@alien8.de \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--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 \
--cc=yu.c.chen@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®