linux-kernel - Re: [PATCH v3 17/26] x86/resctrl: Build a lookup table for each resctrl event id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7bb97892-16fd-49c5-90f0-223526ebdf4c@intel.com>
Date: Fri, 18 Apr 2025 17:48:45 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Tony Luck <tony.luck@...el.com>, Fenghua Yu <fenghuay@...dia.com>, "Maciej
 Wieczor-Retman" <maciej.wieczor-retman@...el.com>, Peter Newman
	<peternewman@...gle.com>, James Morse <james.morse@....com>, Babu Moger
	<babu.moger@....com>, Drew Fustini <dfustini@...libre.com>, Dave Martin
	<Dave.Martin@....com>, Anil Keshavamurthy <anil.s.keshavamurthy@...el.com>
CC: <linux-kernel@...r.kernel.org>, <patches@...ts.linux.dev>
Subject: Re: [PATCH v3 17/26] x86/resctrl: Build a lookup table for each
 resctrl event id

Hi Tony,

On 4/7/25 4:40 PM, Tony Luck wrote:
> User requests to read events arrive from the file system layer
> with a domain id, RMID, and resctrl event id. Responding to
> those requests needs information from various structures.
> 
> Build a quick lookup table indexed by resctrl event id.

Why is a second lookup table needed? What about the
lookup table ("all_events") that patch #2 introduced?

Perhaps struct mon_evt could get a "void *priv" or related
member that points to event's private data that varies by
type of event?

Reinette