Am 5. Mai 2026 14:58:40 UTC schrieb Michael Tokarev <[email protected]>:
>On 13.04.2026 14:30, Bernhard Beschow wrote:
>> + qemu-stable
>
>Hi!
>
>A bit late reply, but here it goes.
>
>What do you recommend for 10.0.x series and this patch?
>This change (commit 774e6f5c15) contextually depends on a
>previous commit in the same area, v10.0.0-1542-gea585b1022
>"hw/ppc/e500: Move clock and TB frequency to machine class".
>
>Should I pick both to 10.0.x, or neither, or modify 774e6f5c15
>to apply without ea585b1022? Do these patches have effect on
>migration stream?
>
>What do yo think?
IMO you made the correct choice for 10.0. Migration should not be affected
since the dtb is created in RAM which gets restored by the migration stream.
The new dtb will be effective only after a reset, i.e. a power cycle.
Sorry for the late reply and thanks for backporting!
Best regards,
Bernhard
>
>Thanks,
>
>/mjt
>
>> Am 11. April 2026 15:45:35 UTC schrieb Vivien LEGER <[email protected]>:
>>> The bus-frequency property in the CPU FDT node was hardcoded to 0.
>>> This is incorrect - it should reflect the actual platform bus clock
>>> frequency, as firmware and RTOSes use it to derive peripheral clock
>>> rates.
>>>
>>> Notably, the RTEMS QorIQ BSP uses bus-frequency to program the MPIC
>>> global timer interval. With bus-frequency=0, the timer interval
>>> overflows to ~85 seconds, preventing any clock interrupts from firing.
>>>
>>> Fix by adding a bus_freq field to PPCE500MachineClass and using it in
>>> the FDT generator. Set bus_freq = PLATFORM_CLK_FREQ_HZ (400MHz) for
>>> existing machines, matching the existing clock_freq value.
>>>
>>> Signed-off-by: Vivien LEGER <[email protected]>
>>> ---
>>> hw/ppc/e500.c | 2 +-
>>> hw/ppc/e500.h | 1 +
>>> hw/ppc/e500plat.c | 1 +
>>> hw/ppc/mpc8544ds.c | 1 +
>>> 4 files changed, 4 insertions(+), 1 deletion(-)
