public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
	 Rex Nie <rex.nie@jaguarmicro.com>
Cc: "james.morse@arm.com" <james.morse@arm.com>,
	 "fenghua.yu@intel.com" <fenghua.yu@intel.com>,
	 "reinette.chatre@intel.com" <reinette.chatre@intel.com>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	 Liming Wu <liming.wu@jaguar.com>
Subject: Re: 答复: [PATCH] fs/resctrl: fix domid loss precision issue
Date: Mon, 11 Mar 2024 14:17:48 +0200 (EET)	[thread overview]
Message-ID: <dcef573e-dada-efdc-32d0-8e6070af9d99@linux.intel.com> (raw)
In-Reply-To: <3fjeeggediya7cl26snya5o5oif6x2xfd26qmsvroe6jygtufu@whanfahntydy>

On Mon, 11 Mar 2024, Maciej Wieczor-Retman wrote:

> Thanks for the reply,
> 
> On 2024-03-11 at 09:37:37 +0000, Rex Nie wrote:
> >Hello,
> >	Please kindly check my inline reply. Thanks.
> >Best regards
> >Rex Nie
> >
> >> >This will cause below issue if cache_id > 0x3fff likes:
> >> 
> >> Is there some reason for cache_id ever being this high?
> >> 
> >> I thought the max for cache_id was the amount of L3 caches on a system. And I
> >> only observed it going up to 3 on some server platforms. So not nearly in the
> >> range of 0x3fff or 16k.
> >> 
> >It is exactly as you said on X86 platforms, but cache_Id on Arm platform is different.
> >According to ACPI for mpam, cache id is used as locator for cache MSC. Reference to RD_PPTT_CACHE_ID definition from edk2-platforms:
> >#define RD_PPTT_CACHE_ID(PackageId, ClusterId, CoreId, CacheType)         \
> >	(                                                              \
> >	  (((PackageId) & 0xF) << 20) | (((ClusterId) & 0xFF) << 12) |              \
> >	  (((CoreId) & 0xFF) << 4) | ((CacheType) & 0xF)                        \
> >	)
> >So it may be > 0x3fff on Arm platform.

Hi Rex,

Please also put that kind of knowledge into the commit message upfront. No 
need to be as verbose as you're here (with code quotes, etc.) but stating 
that some platforms use higher IDs (e.g., Arm) would be pretty useful in 
answering the question why you're doing this change (which is one of the 
key points of describing your change).

-- 
 i.

> >Reference RD_PPTT_CACHE_ID from edk2-platforms: https://github.com/tianocore/edk2-platforms/blob/master/Platform/ARM/SgiPkg/Include/SgiAcpiHeader.h#L202
> 
> and thanks for clearing it up for me! I browsed some MPAM patches but didn't
> notice cache_id was used differently on ARM.
> 
> >
> >> >/sys/fs/resctrl/mon_groups/p1/mon_data/mon_L3_1048564 # cat
> >> >llc_occupancy
> >> 
> >> How did you get this file to appear? Could you maybe show how your
> >> mon_data directory looks like?
> >> 
> >I found this issue on Arm FVP N1 platform and my N2 platform.
> >
> >Below is the steps on Arm FVP N1:
> >mount -t resctrl resctrl / /sys/fs/resctrl
> >cd /sys/fs/resctrl/mon_data
> >
> >/sys/fs/resctrl/mon_data # ls -l
> >total 0
> >dr-xr-xr-x    2 0        0                0 Mar 11 09:24 mon_L3_1048564
> >
> >cd /sys/fs/resctrl/mon_data # cd mon_L3_1048564
> >/sys/fs/resctrl/mon_data/mon_L3_1048564 # cat llc_occupancy
> >cat: read error: No such file or directory
> >
> >Arm FVP MPAM: https://neoverse-reference-design.docs.arm.com/en/latest/mpam/mpam-resctrl.html#memory-system-resource-partitioning-and-monitoring-mpam
> >
> 
> 


  parent reply	other threads:[~2024-03-11 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  6:48 [PATCH] fs/resctrl: fix domid loss precision issue Rex Nie
2024-03-11  8:24 ` Maciej Wieczor-Retman
2024-03-11  9:37   ` 答复: " Rex Nie
2024-03-11 11:49     ` Maciej Wieczor-Retman
2024-03-11 12:13       ` 答复: " Rex Nie
2024-03-11 12:17       ` Ilpo Järvinen [this message]
2024-03-11 12:31         ` Rex Nie

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=dcef573e-dada-efdc-32d0-8e6070af9d99@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=james.morse@arm.com \
    --cc=liming.wu@jaguar.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=reinette.chatre@intel.com \
    --cc=rex.nie@jaguarmicro.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