From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: Jason Andryuk <jason.andryuk@amd.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Yann Sionneau <yann.sionneau@vates.tech>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xenbus: Use .freeze/.thaw to handle xenbus devices
Date: Tue, 25 Nov 2025 11:47:37 +0100 [thread overview]
Message-ID: <aSWJSb4OK645r3tk@mail-itl> (raw)
In-Reply-To: <1c991699-51b7-4284-8179-6bc78f8f4eac@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2626 bytes --]
On Tue, Nov 25, 2025 at 09:20:55AM +0100, Jürgen Groß wrote:
> On 19.11.25 23:47, Jason Andryuk wrote:
> > The goal is to fix s2idle and S3 for Xen PV devices. A domain resuming
> > from s3 or s2idle disconnects its PV devices during resume. The
> > backends are not expecting this and do not reconnect.
> >
> > b3e96c0c7562 ("xen: use freeze/restore/thaw PM events for suspend/
> > resume/chkpt") changed xen_suspend()/do_suspend() from
> > PMSG_SUSPEND/PMSG_RESUME to PMSG_FREEZE/PMSG_THAW/PMSG_RESTORE, but the
> > suspend/resume callbacks remained.
> >
> > .freeze/restore are used with hiberation where Linux restarts in a new
> > place in the future. .suspend/resume are useful for runtime power
> > management for the duration of a boot.
> >
> > The current behavior of the callbacks works for an xl save/restore or
> > live migration where the domain is restored/migrated to a new location
> > and connecting to a not-already-connected backend.
> >
> > Change xenbus_pm_ops to use .freeze/thaw/restore and drop the
> > .suspend/resume hook. This matches the use in drivers/xen/manage.c for
> > save/restore and live migration. With .suspend/resume empty, PV devices
> > are left connected during s2idle and s3, so PV devices are not changed
> > and work after resume.
> >
> > Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
>
> Acked-by: Juergen Gross <jgross@suse.com>
>
> Marek, could you please give this patch a try with QubesOS? I think this
> patch should be verified not to break your use cases regarding suspend /
> resume.
Sure, but I can't promise it will be this week, I have some deadlines to
meet...
> Juergen
>
> > ---
> > drivers/xen/xenbus/xenbus_probe_frontend.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/drivers/xen/xenbus/xenbus_probe_frontend.c b/drivers/xen/xenbus/xenbus_probe_frontend.c
> > index 6d1819269cbe..199917b6f77c 100644
> > --- a/drivers/xen/xenbus/xenbus_probe_frontend.c
> > +++ b/drivers/xen/xenbus/xenbus_probe_frontend.c
> > @@ -148,11 +148,9 @@ static void xenbus_frontend_dev_shutdown(struct device *_dev)
> > }
> > static const struct dev_pm_ops xenbus_pm_ops = {
> > - .suspend = xenbus_dev_suspend,
> > - .resume = xenbus_frontend_dev_resume,
> > .freeze = xenbus_dev_suspend,
> > .thaw = xenbus_dev_cancel,
> > - .restore = xenbus_dev_resume,
> > + .restore = xenbus_frontend_dev_resume,
> > };
> > static struct xen_bus_type xenbus_frontend = {
>
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-11-25 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251119224731.61497-1-jason.andryuk@amd.com>
2025-11-19 22:47 ` [PATCH 1/2] xenbus: Use .freeze/.thaw to handle xenbus devices Jason Andryuk
2025-11-25 8:20 ` Jürgen Groß
2025-11-25 10:47 ` Marek Marczykowski-Górecki [this message]
2025-11-30 2:56 ` Marek Marczykowski-Górecki
2025-11-26 15:00 ` Yann Sionneau
2025-12-01 17:15 ` Jason Andryuk
2025-11-30 2:03 ` Marek Marczykowski-Górecki
2025-12-01 18:20 ` Jason Andryuk
2025-12-01 22:16 ` Marek Marczykowski-Górecki
2025-12-03 22:33 ` Jason Andryuk
2025-11-19 22:47 ` [PATCH 2/2] xenbus: Rename helpers to freeze/thaw/restore Jason Andryuk
2025-11-25 9:17 ` Jürgen Groß
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aSWJSb4OK645r3tk@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=jason.andryuk@amd.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yann.sionneau@vates.tech \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.