Re: [PATCH v3 2/6] perf dso: Allow reading DSO data from an explicit file

[sashiko-bot@kernel.org]

> From: Alireza Haghdoost <haghdoost@uber.com>
> 
> The DSO data cache derives the file to open from the DSO's binary type,
> which can resolve to the runtime image rather than the file a symbol
> table was read from. With split debuginfo, offsets taken from the
> debuginfo file (for example string-table offsets) are then applied to an
> unrelated file.
> 
> Add dso__data_set_path() so a DSO can be configured to read from one
> exact file while keeping the data cache's descriptor eviction and
> reopening. Such DSOs may be owned privately rather than being part of a
> dsos collection, so drop the assertion that every opened data DSO is in
> one.
> 
> Add a DSO data test that reads through an explicit path, closes the
> descriptor, and reads an uncached offset to exercise reopening.
> 
> Signed-off-by: Alireza Haghdoost <haghdoost@uber.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260925-perf-symbol-memory-send-v3-0-3e4e234c363b@uber.com?part=2