From: Greg Kurz <groug@kaod.org>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: kvm-ppc@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>,
kvm@vger.kernel.org,
Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/3] KVM: PPC: Book3S HV: XIVE: do not test the EQ flag validity when resetting
Date: Mon, 20 May 2019 10:06:54 +0200 [thread overview]
Message-ID: <20190520100654.4da6574a@bahia.lan> (raw)
In-Reply-To: <20190520071514.9308-3-clg@kaod.org>
On Mon, 20 May 2019 09:15:13 +0200
Cédric Le Goater <clg@kaod.org> wrote:
> When a CPU is hot-unplugged, the EQ is deconfigured using a zero size
> and a zero address. In this case, there is no need to check the flag
> and queue size validity. Move the checks after the queue reset code
> section to fix CPU hot-unplug.
>
> Reported-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> Tested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> ---
Reviewed-by: Greg Kurz <groug@kaod.org>
> arch/powerpc/kvm/book3s_xive_native.c | 36 +++++++++++++--------------
> 1 file changed, 18 insertions(+), 18 deletions(-)
>
> diff --git a/arch/powerpc/kvm/book3s_xive_native.c b/arch/powerpc/kvm/book3s_xive_native.c
> index 796d86549cfe..3fdea6bf4e97 100644
> --- a/arch/powerpc/kvm/book3s_xive_native.c
> +++ b/arch/powerpc/kvm/book3s_xive_native.c
> @@ -565,24 +565,6 @@ static int kvmppc_xive_native_set_queue_config(struct kvmppc_xive *xive,
> __func__, server, priority, kvm_eq.flags,
> kvm_eq.qshift, kvm_eq.qaddr, kvm_eq.qtoggle, kvm_eq.qindex);
>
> - /*
> - * sPAPR specifies a "Unconditional Notify (n) flag" for the
> - * H_INT_SET_QUEUE_CONFIG hcall which forces notification
> - * without using the coalescing mechanisms provided by the
> - * XIVE END ESBs. This is required on KVM as notification
> - * using the END ESBs is not supported.
> - */
> - if (kvm_eq.flags != KVM_XIVE_EQ_ALWAYS_NOTIFY) {
> - pr_err("invalid flags %d\n", kvm_eq.flags);
> - return -EINVAL;
> - }
> -
> - rc = xive_native_validate_queue_size(kvm_eq.qshift);
> - if (rc) {
> - pr_err("invalid queue size %d\n", kvm_eq.qshift);
> - return rc;
> - }
> -
> /* reset queue and disable queueing */
> if (!kvm_eq.qshift) {
> q->guest_qaddr = 0;
> @@ -604,6 +586,24 @@ static int kvmppc_xive_native_set_queue_config(struct kvmppc_xive *xive,
> return 0;
> }
>
> + /*
> + * sPAPR specifies a "Unconditional Notify (n) flag" for the
> + * H_INT_SET_QUEUE_CONFIG hcall which forces notification
> + * without using the coalescing mechanisms provided by the
> + * XIVE END ESBs. This is required on KVM as notification
> + * using the END ESBs is not supported.
> + */
> + if (kvm_eq.flags != KVM_XIVE_EQ_ALWAYS_NOTIFY) {
> + pr_err("invalid flags %d\n", kvm_eq.flags);
> + return -EINVAL;
> + }
> +
> + rc = xive_native_validate_queue_size(kvm_eq.qshift);
> + if (rc) {
> + pr_err("invalid queue size %d\n", kvm_eq.qshift);
> + return rc;
> + }
> +
> if (kvm_eq.qaddr & ((1ull << kvm_eq.qshift) - 1)) {
> pr_err("queue page is not aligned %llx/%llx\n", kvm_eq.qaddr,
> 1ull << kvm_eq.qshift);
next prev parent reply other threads:[~2019-05-20 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 7:15 [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits Cédric Le Goater
2019-05-20 7:15 ` [PATCH 1/3] KVM: PPC: Book3S HV: XIVE: clear file mapping when device is released Cédric Le Goater
2019-05-20 7:15 ` [PATCH 2/3] KVM: PPC: Book3S HV: XIVE: do not test the EQ flag validity when resetting Cédric Le Goater
2019-05-20 8:06 ` Greg Kurz [this message]
2019-05-20 7:15 ` [PATCH 3/3] KVM: PPC: Book3S HV: XIVE: fix the enforced limit on the vCPU identifier Cédric Le Goater
2019-05-20 9:23 ` Greg Kurz
2019-05-22 23:30 ` [PATCH 0/3] KVM: PPC: Book3S HV: XIVE: assorted fixes on vCPU and RAM limits David Gibson
2019-05-23 6:01 ` Greg Kurz
2019-05-23 6:27 ` David Gibson
2019-05-23 12:44 ` Greg Kurz
2019-05-23 6:06 ` Cédric Le Goater
2019-05-31 6:33 ` Paul Mackerras
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=20190520100654.4da6574a@bahia.lan \
--to=groug@kaod.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sathnaga@linux.vnet.ibm.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