Message ID | 20220811151413.3350684-1-alex.bennee@linaro.org |
---|---|
Headers | show |
Series | memory leaks and speed tweaks | expand |
On Thu, 11 Aug 2022 at 16:24, Alex Bennée <alex.bennee@linaro.org> wrote: > > Hi, > > I've been collecting a number of small fixes since the tree was > frozen. I've been mostly focusing on improving the reliability of the > avocado tests and seeing if there are any low hanging fruit for > improving the performance. > Alex Bennée (8): > linux-user: un-parent OBJECT(cpu) when closing thread > cpu: cache CPUClass in CPUState for hot code paths > hw/core/cpu-sysemu: used cached class in cpu_asidx_from_attrs > cputlb: used cached CPUClass in our hot-paths > ssi: cache SSIPeripheralClass to avoid GET_CLASS() > tests/avocado: add timeout to the aspeed tests > tests/avocado: apply a band aid to aspeed-evb login > accel/tcg: remove trace_vcpu_dstate TB checking Changes to tests/ is fine, and fixes for memory leaks also if they've been well tested, but stuff like the caching of class objects is really not 7.1 material at this point in the release cycle, I think. thanks -- PMM
Peter Maydell <peter.maydell@linaro.org> writes: > On Thu, 11 Aug 2022 at 16:24, Alex Bennée <alex.bennee@linaro.org> wrote: >> >> Hi, >> >> I've been collecting a number of small fixes since the tree was >> frozen. I've been mostly focusing on improving the reliability of the >> avocado tests and seeing if there are any low hanging fruit for >> improving the performance. > >> Alex Bennée (8): >> linux-user: un-parent OBJECT(cpu) when closing thread >> cpu: cache CPUClass in CPUState for hot code paths >> hw/core/cpu-sysemu: used cached class in cpu_asidx_from_attrs >> cputlb: used cached CPUClass in our hot-paths >> ssi: cache SSIPeripheralClass to avoid GET_CLASS() >> tests/avocado: add timeout to the aspeed tests >> tests/avocado: apply a band aid to aspeed-evb login >> accel/tcg: remove trace_vcpu_dstate TB checking > > Changes to tests/ is fine, and fixes for memory leaks > also if they've been well tested, but stuff like the > caching of class objects is really not 7.1 material > at this point in the release cycle, I think. No worries - I can drop the caching stuff for 7.1 but at least people can test it ;-)