On Thu, Dec 05, 2024 at 04:26:55PM +0530, Sibi Sankar wrote: > On 11/22/24 14:07, Johan Hovold wrote: > > I have a Lenovo ThinkPad T14s set up now so I gave this series a spin > > there too, and there I do *not* see the above mentioned -EOPNOSUPP error > > and the memlat driver probes successfully. > > > > On the other hand, this series seems to have no effect on a kernel > > compilation benchmark. Is that expected? > > I can have a look at your tree. But memlat in general > depends on the cpu frequency when your benchmarks max > the cpu's the ddr/llcc are scaled accordingly by it. A kernel compilation should max out the CPU frequency on all cores. > > And does this mean that you should stick with the uppercase "MEMLAT" > > string after all? The firmware on my CRD is not the latest one, but I am > > using the latest available firmware for the T14s. > > We should stick with "memlat" if we run into a device in the > wild that doesn't support "MEMLAT" Ok. So the updated firmware supports both strings? Johan
