[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4244b729-2eec-4999-9427-00b5c9f3e6fc@intel.com>
Date: Fri, 29 Mar 2024 16:06:12 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Haifeng Xu <haifeng.xu@...pee.com>, <james.morse@....com>
CC: <fenghua.yu@...el.com>, <babu.moger@....com>, <bp@...en8.de>,
<tglx@...utronix.de>, <mingo@...hat.com>, <dave.hansen@...ux.intel.com>,
<hpa@...or.com>, <peternewman@...gle.com>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>, <corbet@....net>, <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v6 0/2] x86/resctrl: Track llc_occupancy of RMIDs in limbo
list
Hi Haifeng,
On 3/19/2024 1:30 AM, Haifeng Xu wrote:
> After removing a monitor group, its RMID may not be freed immediately
> unless its llc_occupancy is less than the re-allocation threshold. If
> turning up the threshold, the RMID can be reused. In order to know how
> much the threshold should be, it's necessary to acquire the llc_occupancy.
>
> The patch series provides a new tracepoint to track the llc_occupancy.
There seems to be a problem with the DKIM attestation. Here is what I see
when I download this series:
$ b4 am -Q 20240319083039.223088-1-haifeng.xu@...pee.com
Grabbing thread from lore.kernel.org/all/20240319083039.223088-1-haifeng.xu@...pee.com/t.mbox.gz
Analyzing 3 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Checking attestation on all messages, may take a moment...
---
✗ [PATCH v6 1/2] x86/resctrl: Rename pseudo_lock_event.h to trace.h
✗ [PATCH v6 2/2] x86/resctrl: Add tracepoint for llc_occupancy tracking
---
✗ BADSIG: DKIM/shopee.com
---
Total patches: 2
---
The patches look good to me. Thank you very much for adding this.
Please resubmit with the DKIM attestation fixed and then you can add:
| Reviewed-by: Reinette Chatre <reinette.chatre@...el.com>
Reinette
Powered by blists - more mailing lists