Bug 2182742 - [RFE] - lscpu - please add support for Intel Sapphire Rapids HBM Cache mode
Summary: [RFE] - lscpu - please add support for Intel Sapphire Rapids HBM Cache mode
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: util-linux
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Radka Brychtova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-29 14:04 UTC by Jiri Hladky
Modified: 2023-08-09 09:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-153419 0 None None None 2023-03-29 14:05:20 UTC

Description Jiri Hladky 2023-03-29 14:04:37 UTC
Description of problem:

Hello, 

Intel Sapphire Rapids platform introduces HBM-enabled CPUs. HBM can be operated in Cached Mode - HBM caches DDR.
https://www.intel.ca/content/www/ca/en/products/docs/processors/xeon/xeon-max-series-product-brief.html

lscpu gives information about the CPU caches but does not provide any info about the HBM Cache.

We want to enhance lscpu to close this gap. 

FYI, lstopo from hwloc package shows the HBM Cache (MemCache line below, generated on intel-eaglestream-spr-17.khw3.lab.eng.bos.redhat.com server). 
$lstopo 
Machine (1007GB total)
  Package L#0
    MemCache L#0 (64GB)
      NUMANode L#0 (P#0 503GB)

In Kernel, the Cache is described in sysfs as "memory_side_cache" dir:
/sys/devices/system/node/node0/memory_side_cache/index1

Please also refer to the documentation here:
https://docs.kernel.org/admin-guide/mm/numaperf.html

Thanks a lot
Jirka

Comment 2 Karel Zak 2023-08-09 09:36:23 UTC
This should be implemented upstream, rather than as RHEL specific patch.

Added to the upstream issue tracker: https://github.com/util-linux/util-linux/issues/2426


Note You need to log in before you can comment on or make changes to this bug.