From: Babu Moger <babu.moger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
"Moger, Babu" <bmoger@amd.com>,
tony.luck@intel.com, Dave.Martin@arm.com, james.morse@arm.com,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com
Cc: x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
peternewman@google.com, eranian@google.com,
gautham.shenoy@amd.com
Subject: Re: [PATCH] x86/resctrl: Fix buggy overflow when reactivating previously Unavailable RMID
Date: Wed, 8 Oct 2025 13:08:36 -0500 [thread overview]
Message-ID: <6c512e5a-0657-4f3e-83ac-7f8fa1de4c6c@amd.com> (raw)
In-Reply-To: <1b352ad2-e542-4005-a470-5a9bb94b7ad8@intel.com>
Hi Reinette,
On 10/7/25 22:04, Reinette Chatre wrote:
> Hi Babu,
>
> On 10/7/25 4:47 PM, Moger, Babu wrote:
>> On 10/7/2025 3:23 PM, Reinette Chatre wrote:
>>> On 10/6/25 4:13 PM, Babu Moger wrote:
> ...
>
>>>> ---
>>>>
>>>> Tested this on multiple AMD systems, but not on Intel systems.
>>>> Need help with that. If everything goes well, this patch needs to
>>>> go to all the stable kernels.
>>> Needs a "Fixes" and "Cc: stable@vger.kernel.org"?
>> Hmm.. Not sure. Which commit to add Fixes in. This is AMD related.
>> We should have taken care when adding support to AMD. Does this commit make sense?
>>
>> Fixes: 4d05bf71f157d ("x86/resctrl: Introduce AMD QOS feature")
> This seems fair. From what I can tell this spans all LTS kernels so I expect
> a couple of different variants of this fix since this code has evolved quite a lot.
> Do you want this fix backported to all the LTS kernels?
> It may be useful to add a note to the stable team that this patch needs changes to
> apply to all kernel versions (see "Point out known problems"
> in Documentation/process/stable-kernel-rules.rst)
Sure. Sending v2 will all the updates.
--
Thanks
Babu Moger
next prev parent reply other threads:[~2025-10-08 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 23:13 [PATCH] x86/resctrl: Fix buggy overflow when reactivating previously Unavailable RMID Babu Moger
2025-10-07 20:23 ` Reinette Chatre
2025-10-07 23:47 ` Moger, Babu
2025-10-08 3:04 ` Reinette Chatre
2025-10-08 18:08 ` Babu Moger [this message]
2025-10-08 15:23 ` Dave Martin
2025-10-08 18:42 ` Babu Moger
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=6c512e5a-0657-4f3e-83ac-7f8fa1de4c6c@amd.com \
--to=babu.moger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=bmoger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=gautham.shenoy@amd.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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