Hi Juergen,

> On Wed, 2022-11-02 at 16:00 +0100, Juergen Gross wrote:
> > Today all timers are migrated to cpu 0 when the system is being
> > suspended. They are not migrated back after resuming the system
> > again.
> >
> > This results (at least) to visible problems with the credit
> > scheduler,
> > as the timer isn't handled on the cpu it was expected to occur, which
> > will result in an ASSERT() triggering. Other more subtle problems,
> > like
> > uninterrupted elongated time slices, are probable. The least effect
> > will be worse performance on cpu 0 resulting from most scheduling
> > related timer interrupts happening there after suspend/resume.
> >
> > Add migrating the scheduling related timers of a specific cpu from
> > cpu
> > 0 back to its original cpu when that cpu has gone up when resuming
> > the
> > system.
> >
> > Fixes: 0763cd268789 ("xen/sched: don't disable scheduler on cpus
> > during suspend")
> > Signed-off-by: Juergen Gross <jgr...@suse.com>
> > Tested-by: Marek Marczykowski-Górecki
> > <marma...@invisiblethingslab.com>
> >
> Acked-by: Dario Faggioli <dfaggi...@suse.com>

Release-acked-by: Henry Wang <henry.w...@arm.com>

Kind regards,
Henry

Reply via email to