From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: borntraeger@de.ibm.com, thuth@redhat.com, david@redhat.com,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
scgl@linux.ibm.com, seiden@linux.ibm.com, nrb@linux.ibm.com
Subject: Re: [PATCH v16 0/6] KVM: s390: pv: implement lazy destroy for reboot
Date: Tue, 15 Nov 2022 09:42:36 +0100 [thread overview]
Message-ID: <d9d73722-f1f5-3ba9-e9f5-538ee4f4ba2e@linux.ibm.com> (raw)
In-Reply-To: <20221111170632.77622-1-imbrenda@linux.ibm.com>
On 11/11/22 18:06, Claudio Imbrenda wrote:
> Previously, when a protected VM was rebooted or when it was shut down,
> its memory was made unprotected, and then the protected VM itself was
> destroyed. Looping over the whole address space can take some time,
> considering the overhead of the various Ultravisor Calls (UVCs). This
> means that a reboot or a shutdown would take a potentially long amount
> of time, depending on the amount of used memory.
>
Well, this was a journey :)
Thanks, picked
prev parent reply other threads:[~2022-11-15 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 17:06 [PATCH v16 0/6] KVM: s390: pv: implement lazy destroy for reboot Claudio Imbrenda
2022-11-11 17:06 ` [PATCH v16 1/6] KVM: s390: pv: asynchronous " Claudio Imbrenda
2022-11-11 17:06 ` [PATCH v16 2/6] KVM: s390: pv: api documentation for asynchronous destroy Claudio Imbrenda
2022-11-11 17:06 ` [PATCH v16 3/6] KVM: s390: pv: add KVM_CAP_S390_PROTECTED_ASYNC_DISABLE Claudio Imbrenda
2022-11-11 17:06 ` [PATCH v16 4/6] KVM: s390: pv: avoid export before import if possible Claudio Imbrenda
2022-11-11 17:06 ` [PATCH v16 5/6] KVM: s390: pv: support for Destroy fast UVC Claudio Imbrenda
2022-11-11 17:06 ` [PATCH v16 6/6] KVM: s390: pv: module parameter to fence asynchronous destroy Claudio Imbrenda
2022-11-15 8:42 ` Janosch Frank [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=d9d73722-f1f5-3ba9-e9f5-538ee4f4ba2e@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=scgl@linux.ibm.com \
--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