From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
groug@kaod.org, joserz@linux.vnet.ibm.com, surajjs@au1.ibm.com,
sam.bobroff@au1.ibm.com
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] target/ppc: Clarify compat mode max_threads value
Date: Mon, 15 Jan 2018 08:52:27 +0100 [thread overview]
Message-ID: <62a187bb-cc00-7210-ea81-bcca2fc75c06@redhat.com> (raw)
In-Reply-To: <20180115072715.25921-2-david@gibson.dropbear.id.au>
On 15/01/2018 08:27, David Gibson wrote:
> We recently had some discussions that were sidetracked for a while, because
> nearly everyone misapprehended the purpose of the 'max_threads' field in
> the compatiblity modes table. It's all about guest expectations, not host
> expectations or support (that's handled elsewhere).
>
> In an attempt to avoid a repeat of that confusion, rename the field to
> 'max_vthreads' and add an explanatory comment.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> hw/ppc/spapr.c | 4 ++--
> target/ppc/compat.c | 25 +++++++++++++++++--------
> target/ppc/cpu.h | 2 +-
> 3 files changed, 20 insertions(+), 11 deletions(-)
>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
next prev parent reply other threads:[~2018-01-15 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 7:27 [Qemu-devel] [PATCH 0/2] Further VSMT fixes David Gibson
2018-01-15 7:27 ` [Qemu-devel] [PATCH 1/2] target/ppc: Clarify compat mode max_threads value David Gibson
2018-01-15 7:52 ` Laurent Vivier [this message]
2018-01-15 8:45 ` Greg Kurz
2018-01-15 10:40 ` joserz
2018-01-15 7:27 ` [Qemu-devel] [PATCH 2/2] spapr: Adjust default VSMT value for better migration compatibility David Gibson
2018-01-15 7:53 ` Laurent Vivier
2018-01-15 9:48 ` Greg Kurz
2018-01-16 4:42 ` David Gibson
2018-01-15 10:38 ` joserz
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=62a187bb-cc00-7210-ea81-bcca2fc75c06@redhat.com \
--to=lvivier@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=joserz@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.bobroff@au1.ibm.com \
--cc=surajjs@au1.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.