From: Steffen Eiden <seiden@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: borntraeger@de.ibm.com, frankja@linux.ibm.com, thuth@redhat.com,
david@redhat.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, scgl@linux.ibm.com,
nrb@linux.ibm.com
Subject: Re: [PATCH v14 6/6] KVM: s390: pv: module parameter to fence asynchronous destroy
Date: Tue, 4 Oct 2022 15:48:08 +0200 [thread overview]
Message-ID: <e183d9b5-eb39-1e08-1d23-831a2df2e0e6@linux.ibm.com> (raw)
In-Reply-To: <20220930140150.37463-7-imbrenda@linux.ibm.com>
On 9/30/22 16:01, Claudio Imbrenda wrote:
> Add the module parameter "async_destroy", to allow the asynchronous
> destroy mechanism to be switched off. This might be useful for
> debugging purposes.
>
> The parameter is enabled by default since the feature is opt-in anyway.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
LGTM
Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
> ---
> arch/s390/kvm/kvm-s390.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 7a3bd68efd85..33a53b389cf3 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -209,7 +209,13 @@ unsigned int diag9c_forwarding_hz;
> module_param(diag9c_forwarding_hz, uint, 0644);
> MODULE_PARM_DESC(diag9c_forwarding_hz, "Maximum diag9c forwarding per second, 0 to turn off");
>
> -static int async_destroy;
> +/*
> + * allow asynchronous deinit for protected guests; enable by default since
> + * the feature is opt-in anyway
> + */
> +static int async_destroy = 1;
> +module_param(async_destroy, int, 0444);
> +MODULE_PARM_DESC(async_destroy, "Asynchronous destroy for protected guests");
>
> /*
> * For now we handle at most 16 double words as this is what the s390 base
prev parent reply other threads:[~2022-10-04 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 14:01 [PATCH v14 0/6] KVM: s390: pv: implement lazy destroy for reboot Claudio Imbrenda
2022-09-30 14:01 ` [PATCH v14 1/6] KVM: s390: pv: asynchronous " Claudio Imbrenda
2022-10-04 13:43 ` Steffen Eiden
2022-10-04 16:56 ` Claudio Imbrenda
2022-10-10 11:38 ` Janosch Frank
2022-09-30 14:01 ` [PATCH v14 2/6] KVM: s390: pv: api documentation for asynchronous destroy Claudio Imbrenda
2022-10-04 13:43 ` Steffen Eiden
2022-10-10 11:41 ` Janosch Frank
2022-09-30 14:01 ` [PATCH v14 3/6] KVM: s390: pv: add KVM_CAP_S390_PROTECTED_ASYNC_DISABLE Claudio Imbrenda
2022-10-04 13:44 ` Steffen Eiden
2022-10-10 11:45 ` Janosch Frank
2022-10-10 12:15 ` Claudio Imbrenda
2022-10-10 13:10 ` Janosch Frank
2022-09-30 14:01 ` [PATCH v14 4/6] KVM: s390: pv: avoid export before import if possible Claudio Imbrenda
2022-10-04 13:47 ` Steffen Eiden
2022-09-30 14:01 ` [PATCH v14 5/6] KVM: s390: pv: support for Destroy fast UVC Claudio Imbrenda
2022-10-04 13:48 ` Steffen Eiden
2022-09-30 14:01 ` [PATCH v14 6/6] KVM: s390: pv: module parameter to fence asynchronous destroy Claudio Imbrenda
2022-10-04 13:48 ` Steffen Eiden [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=e183d9b5-eb39-1e08-1d23-831a2df2e0e6@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.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=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