On Wed, Jun 11, 2025 at 1:39 PM Oleksii Kurochko <[email protected]> wrote: > > Hello Mykola, > > On 6/11/25 9:03 AM, Mykola Kvach wrote: > > === ARM === > > * SMMU handling for PCIe Passthrough on ARM (v11) > - Mykyta Poturai > - > https://lore.kernel.org/xen-devel/[email protected]/ > - > https://patchew.org/Xen/[email protected]/ > > * xen/arm: scmi: introduce SCI SCMI SMC multi-agent support > - Grygorii Strashko > - > https://lore.kernel.org/xen-devel/[email protected]/ > > * Add initial Xen Suspend-to-RAM support on ARM64 (v4) > - Mykola Kvach > - > https://lore.kernel.org/xen-devel/[email protected]/ > - https://patchew.org/Xen/[email protected]/ > > I'd like to propose including initial support for Suspend-to-RAM in Xen 4.21. > > This feature enables Xen and its guests to enter suspend state via > PSCI SYSTEM_SUSPEND. Xen suspend is triggered from the hardware domain. > > Support is currently Experimental. > > Thanks for your feedback! > > I saw that there are two patch series connected to Suspend-to-RAM topic: > - > https://lore.kernel.org/xen-devel/[email protected]/ > - > https://lore.kernel.org/xen-devel/[email protected]/ > > So it seems like we should follow a progress for these two patch series in > parallel > Or the difference is that one of patch series is for connect to guest and > another > to hardware domains. > > Am I missing something?
Yes, you're right, but the second patch series (part 2) depends on the first one (part 1). It was split out to help speed up the review process, as suggested during the review of v3, in order to separate guest (vPSCI) and host (PSCI) suspend functionality. It's expected that part 1 will be merged first. However, since CONFIG_SYSTEM_SUSPEND has already been merged, most of the patches from part 2 can also be applied independently, except for a few at the end of the series that still rely on part 1. > > ~ Oleksii Best regards, Mykola
