From: Bradley Morgan <brads@mainlining.org>
To: Ard Biesheuvel <ardb@kernel.org>, Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
James Morse <james.morse@arm.com>, Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: hibernate: dust off the suspend/cleanup rework
Date: Fri, 28 Aug 2026 12:31:26 +0100 [thread overview]
Message-ID: <42165318-B65A-4BD4-ADE0-1DBD7F82416B@mainlining.org> (raw)
In-Reply-To: <4cc971de-2fc9-496a-a5f5-002bd6b6bd43@app.fastmail.com>
On 28 August 2026 11:32:27 BST, Ard Biesheuvel <ardb@kernel.org> wrote:
>Hi Bradley,
>
Ard!
>On Tue, 25 Aug 2026, at 22:58, Bradley Morgan wrote:
>> Everything object compiles and passes checkpatch and sparse. I could not
>> boot or run a hibernate cycle on real hardware here, so that still wants
>> doing before anyone gets excited.
>>
>
>You can easily test hibernate under QEMU/mach-virt: just create a file on
>the host, mkswap it and pass it to the VM as a virtio drive (e.g.,
>/dev/vda)
>You can then swapon it in the VM and do 'echo disk >/sys/power/state',
>which
>will perform the hibernate and exit QEMU. If you then restart it with
>'resume=/dev/vda' on the command line, it will perform the resume from
>hibernate at boot.
>
Ack. Tried on PKVM last night.
>I've had a go with your series on a NV capable system (Mac Mini M2).
>Without
>the series applied, I can hibernate and resume 4 vCPUs without issue, so
>it
>is not entirely clear to me what your series intends to fix.
>
>With the series applied resume from hibernate still works - I did see one
>intermittent failure where the secondaries failed to come up, but I only
>saw it once and so I cannot say for certain whether your series triggered
>it or not.
>
>Tested-by: Ard Biesheuvel <ardb@kernel.org>
>
For the whole series?
>
>
>
>
>
>
>
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
prev parent reply other threads:[~2026-08-28 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 20:58 [PATCH 0/7] arm64: hibernate: dust off the suspend/cleanup rework Bradley Morgan
2026-08-25 20:58 ` [PATCH 1/7] arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc Bradley Morgan
2026-08-25 20:58 ` [PATCH 2/7] arm64: head: correct comment for init_kernel_el() Bradley Morgan
2026-08-25 20:58 ` [PATCH 3/7] arm64: hibernate: free MTE tag pages after saving Bradley Morgan
2026-08-25 20:58 ` [PATCH 4/7] arm64: hibernate: fix _cpu_resume() calling convention Bradley Morgan
2026-08-25 20:58 ` [PATCH 5/7] arm64: hibernate: use dcache_by_myline_op Bradley Morgan
2026-08-25 20:58 ` [PATCH 6/7] arm64: hibernate: only clean to PoC Bradley Morgan
2026-08-25 20:58 ` [PATCH 7/7] arm64: hibernate: use regular cpu_resume() logic Bradley Morgan
2026-08-28 10:32 ` [PATCH 0/7] arm64: hibernate: dust off the suspend/cleanup rework Ard Biesheuvel
2026-08-28 11:31 ` Bradley Morgan [this message]
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=42165318-B65A-4BD4-ADE0-1DBD7F82416B@mainlining.org \
--to=brads@mainlining.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox