Re: [PATCH v4][PART 1 4/4] CHANGELOG: Mention Xen suspend/resume to RAM feature on arm64

[Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>]

On 5/27/25 6:05 PM, Mykola Kvach wrote:

> Hi, @Oleksii Kurochko
>
> On Tue, May 27, 2025 at 6:38 PM Oleksii Kurochko
> <oleksii.kurochko@xxxxxxxxx> wrote:
> > Hello Mykola,
> >
> > On 5/27/25 11:18 AM, Mykola Kvach wrote:
> >
> > From: Mykola Kvach <mykola_kvach@xxxxxxxx>
> >
> > Signed-off-by: Mykola Kvach <mykola_kvach@xxxxxxxx>
> > ---
> >  CHANGELOG.md | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/CHANGELOG.md b/CHANGELOG.md
> > index ec452027f5..fc89ed6e09 100644
> > --- a/CHANGELOG.md
> > +++ b/CHANGELOG.md
> > @@ -26,6 +26,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
> >
> >   - On Arm:
> >      - Ability to enable stack protector
> > +    - Support guest suspend/resume to/from RAM
> >
> >  ### Removed
> >   - On x86:
> >
> > According to your commit message, suspend/resume will only work for Arm64.
> > I think it would be good to mention that in the CHANGELOG.md as well.
> >       
> Thank you for pointing that out — in this case, I forgot to drop
> "arm64" from the commit message.
>     
Then it makes sense to me to drop it in next patch series version.

> For non-hardware domain guests, suspend/resume support is available
> for both ARM32 and ARM64.
> When PSCI SYSTEM_SUSPEND is triggered from the hardware domain, the
> system ultimately uses
> Host PSCI — that is, a full system suspend is performed.
>     
Thanks for clarification.

> > Also, this implementation adds suspend/resume support via vPSCI, which
> > I believe is also worth noting in the CHANGELOG.md.
> >       
> You're right — in this context, "guest suspend/resume" refers to
> handling via the virtual PSCI (vPSCI) interface.
> When regular PSCI is used, it's typically referred to as Host PSCI.
> That sentence could probably be rephrased for better clarity. Thank you.
>     
It would be nice.

Thanks.
~ Oleksii