From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, david@redhat.com, thuth@redhat.com,
borntraeger@de.ibm.com, frankja@linux.ibm.com,
pasic@linux.ibm.com, nrb@linux.ibm.com, nsg@linux.ibm.com,
seiden@linux.ibm.com
Subject: [PATCH v3 0/2] s390x/pv: Add support for asynchronous teardown for reboot
Date: Tue, 14 Feb 2023 17:30:33 +0100 [thread overview]
Message-ID: <20230214163035.44104-1-imbrenda@linux.ibm.com> (raw)
The first patch is just a minimal header update to compile the second
patch; it can be safely discarded once the Linux headers are updated to
6.2.
The second patch adds support for asynchronous teardown of protected
guests when rebooting. The existing guest is prepared for asynchronous
teardown, the rebooted guest will be able to continue immediately, while a
background thread actually performs the necessary cleanup.
v2->v3:
* improve description of header updates
* allocate the QemuThread on the stack to avoid leak, and explain why
v1->v2:
* remove useless snprintf and pass the name of the thread directly
* make the name of the thread more understandable
Claudio Imbrenda (2):
Linux header update
s390x/pv: Add support for asynchronous teardown for reboot
hw/s390x/pv.c | 28 ++++++++++++++++++++++++++++
hw/s390x/s390-virtio-ccw.c | 5 ++++-
include/hw/s390x/pv.h | 2 ++
linux-headers/linux/kvm.h | 3 +++
4 files changed, 37 insertions(+), 1 deletion(-)
--
2.39.1
next reply other threads:[~2023-02-14 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:30 Claudio Imbrenda [this message]
2023-02-14 16:30 ` [PATCH v3 1/2] Linux header update Claudio Imbrenda
2023-02-14 16:30 ` [PATCH v3 2/2] s390x/pv: Add support for asynchronous teardown for reboot Claudio Imbrenda
2023-02-16 8:43 ` Thomas Huth
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=20230214163035.44104-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=seiden@linux.ibm.com \
--cc=thuth@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).