Re: [PATCH -next] PM: tools: add "CPU killed" timeline on arm64 platform

[Rafael J. Wysocki]

On Mon, Feb 27, 2023 at 3:27 AM luoxueqin <luoxueqin@xxxxxxxxxx> wrote:
>
> 在 2023/2/24 02:11, Rafael J. Wysocki 写道:
> > On Thu, Feb 23, 2023 at 5:46 AM Xueqin Luo <luoxueqin@xxxxxxxxxx> wrote:
> >>
> >> On the arm64 platform, the core log of cpu offline is as follows:
> >
> > Please spell CPU in capitals.
>
> Thanks for pointing out my mistake.
>
> >
> >> [  100.431501] CPU1: shutdown
> >> [  100.454820] psci: CPU1 killed (polled 20 ms)
> >> [  100.459266] CPU2: shutdown
> >> [  100.482575] psci: CPU2 killed (polled 20 ms)
> >> [  100.486057] CPU3: shutdown
> >> [  100.513974] psci: CPU3 killed (polled 28 ms)
> >> [  100.518068] CPU4: shutdown
> >> [  100.541481] psci: CPU4 killed (polled 24 ms)
> >>
> >> 'smpboot: CPU (?P<cpu>[0-9]*) is now offline' cannot be applied
> >> to the arm64 platform, which caused the loss of the suspend
> >> machine stage in S3.
> >
> > I'm not exactly sure what you mean by "loss of the suspend machine stage in S3".
>
> I made a mistake in saying "loss of the suspend machine stage in S3",
> please allow me to correct it. Because the original program only
> recognized the "CPU up" action on the arm64 platform, in output.html,
> "CPU up" was classified as the "suspend machine" stage. Adding this code
> can put "CPU killed" and "CPU up" in the correct position.

It is still somewhat unclear to be honest.

What does "the original program" above mean?  sleepgraph.py before the patch?

And IIUC the goal of the patch is to prevent sleepgraph from
mistakenly treating the "CPU up" message as part of the suspend flow
(because it should be regarded as part of the resume flow).

If my understanding above is correct, please update the patch
changelog accordingly and resubmit the patch.