From: Greg Kurz <groug@kaod.org>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] spapr: check smp_threads < vsmt
Date: Wed, 7 Feb 2018 21:21:48 +0100 [thread overview]
Message-ID: <20180207212148.73c77de1@bahia.lan> (raw)
In-Reply-To: <20180207161730.17194-1-lvivier@redhat.com>
On Wed, 7 Feb 2018 17:17:30 +0100
Laurent Vivier <lvivier@redhat.com> wrote:
> We ignore silently the value of smp_threads when we set
> the VSMT value, and if smp_threads is greater than VSMT
> kernel is going into trouble later.
>
> Fixes: 8904e5a750
> ("spapr: Adjust default VSMT value for better migration compatibility")
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/ppc/spapr.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index 32a876be56..638b3cafd0 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -2294,15 +2294,7 @@ static void spapr_set_vsmt_mode(sPAPRMachineState *spapr, Error **errp)
> }
>
> /* Detemine the VSMT mode to use: */
> - if (vsmt_user) {
> - if (spapr->vsmt < smp_threads) {
> - error_setg(&local_err, "Cannot support VSMT mode %d"
> - " because it must be >= threads/core (%d)",
> - spapr->vsmt, smp_threads);
In this case, we'd error out because the user requested two settings that
are known to be incompatible.
> - goto out;
> - }
> - /* In this case, spapr->vsmt has been set by the command line */
> - } else {
> + if (!vsmt_user) {
> /*
> * Default VSMT value is tricky, because we need it to be as
> * consistent as possible (for migration), but this requires
> @@ -2313,6 +2305,13 @@ static void spapr_set_vsmt_mode(sPAPRMachineState *spapr, Error **errp)
> spapr->vsmt = 8;
In this case, we'd error out because the user requested a setting that is
incompatible with our default. Maybe worth a separate error message ?
"Cannot support %d threads/core because it must be <= to default VSMT mode (8)"
Anyway, the fix is good:
Reviewed-by: Greg Kurz <groug@kaod.org>
> }
>
> + if (spapr->vsmt < smp_threads) {
> + error_setg(&local_err, "Cannot support VSMT mode %d"
> + " because it must be >= threads/core (%d)",
> + spapr->vsmt, smp_threads);
> + goto out;
> + }
> +
> /* KVM: If necessary, set the SMT mode: */
> if (kvm_enabled() && (spapr->vsmt != kvm_smt)) {
> ret = kvmppc_set_smt_threads(spapr->vsmt);
next prev parent reply other threads:[~2018-02-07 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:17 [Qemu-devel] [PATCH] spapr: check smp_threads < vsmt Laurent Vivier
2018-02-07 20:21 ` Greg Kurz [this message]
2018-02-08 8:49 ` [Qemu-devel] [Qemu-ppc] " Laurent Vivier
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=20180207212148.73c77de1@bahia.lan \
--to=groug@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).