From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Bibo Mao" <maobibo@loongson.cn>,
"QEMU devel" <qemu-devel@nongnu.org>,
"Ani Sinha" <anisinha@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Song Gao" <gaosong@loongson.cn>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Sergio Lopez" <slp@redhat.com>
Subject: Re: [PATCH 0/3] S3 and S4 sleep for loongarch/virt & microvm
Date: Fri, 14 Jun 2024 05:27:25 +0100 [thread overview]
Message-ID: <ac2dbd67-97f7-4748-b545-3d05cb1d9a36@app.fastmail.com> (raw)
In-Reply-To: <002b6625-9fed-beeb-700c-93438023d873@loongson.cn>
在2024年6月14日六月 上午4:32,maobibo写道:
> It is interesting.
>
> How to wakeup VM if it sleeps in S3/S4, from emulated keyboard or
> ethernet magic packet or qemu monitor command in background?
Hi Bibo,
The best way to wake the guest is system_wakeup command in monitor.
Thanks
- Jiaxun
>
> Regards
> Bibo Mao
>
>
> On 2024/6/14 上午1:30, Jiaxun Yang wrote:
>> Hi all,
>>
>> This series implemented S3 and S4 sleep for loongarch virt machine
>> and microvm.
>>
>> For loongarch/virt a kernel patch is requried [1].
>>
>> [1]: https://lore.kernel.org/loongarch/20240613-loongarch64-sleep-v1-0-a245232af5e4@flygoat.com/
>>
>> Please review.
>> Thanks
>>
>> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
>> ---
>> Jiaxun Yang (3):
>> acpi/ged: Implement S3 and S4 sleep
>> hw/loongarch/virt: Wire up S3 and S4 sleep
>> hw/i386/microvm: Wire up S3 and S4 sleep
>>
>> hw/acpi/generic_event_device.c | 70 ++++++++++++++++++++++++++++++----
>> hw/i386/acpi-microvm.c | 18 +++++++++
>> hw/i386/microvm.c | 3 ++
>> hw/loongarch/acpi-build.c | 18 +++++++++
>> hw/loongarch/virt.c | 3 ++
>> include/hw/acpi/generic_event_device.h | 12 +++++-
>> 6 files changed, 115 insertions(+), 9 deletions(-)
>> ---
>> base-commit: f3e8cc47de2bc537d4991e883a85208e4e1c0f98
>> change-id: 20240613-loongarch64-sleep-37b2466b8d76
>>
>> Best regards,
>>
--
- Jiaxun
next prev parent reply other threads:[~2024-06-14 4:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 17:30 [PATCH 0/3] S3 and S4 sleep for loongarch/virt & microvm Jiaxun Yang
2024-06-13 17:30 ` [PATCH 1/3] acpi/ged: Implement S3 and S4 sleep Jiaxun Yang
2024-07-01 20:19 ` Michael S. Tsirkin
2024-07-25 8:22 ` Igor Mammedov
2024-07-25 8:30 ` Michael S. Tsirkin
2024-07-25 8:54 ` Igor Mammedov
2024-06-13 17:30 ` [PATCH 2/3] hw/loongarch/virt: Wire up " Jiaxun Yang
2024-07-25 8:26 ` Igor Mammedov
2024-06-13 17:30 ` [PATCH 3/3] hw/i386/microvm: " Jiaxun Yang
2024-06-14 3:32 ` [PATCH 0/3] S3 and S4 sleep for loongarch/virt & microvm maobibo
2024-06-14 4:27 ` Jiaxun Yang [this message]
2024-06-14 5:17 ` maobibo
2024-06-14 13:55 ` Jiaxun Yang
2024-06-14 14:03 ` Daniel P. Berrangé
2024-06-15 1:45 ` maobibo
2024-07-25 7:52 ` Igor Mammedov
2024-07-25 8:29 ` Igor Mammedov
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=ac2dbd67-97f7-4748-b545-3d05cb1d9a36@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=gaosong@loongson.cn \
--cc=imammedo@redhat.com \
--cc=maobibo@loongson.cn \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=slp@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).