All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] spapr: ensure we have at least one XICS server
Date: Mon, 25 May 2015 11:30:02 +1000	[thread overview]
Message-ID: <20150525013002.GG6255@voom.redhat.com> (raw)
In-Reply-To: <20150513102818.31240.99013.stgit@bahia.huguette.org>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

On Wed, May 13, 2015 at 12:29:33PM +0200, Greg Kurz wrote:
> XICS needs to know the upper value for cpu_index as it is used to compute
> the number of servers:
> 
>     smp_cpus * kvmppc_smt_threads() / smp_threads
> 
> When passing -smp cpus=1,threads=9 on a POWER8 host, we end up with:
> 
>     1 * 8 / 9 = 0
> 
> ... which leads to an assertion in both emulated:
> 
> Number of servers needs to be greater 0
> Aborted (core dumped)
> 
> ... and in-kernel XICS:
> 
> xics_kvm_realize: Assertion `icp->nr_servers' failed.
> Aborted (core dumped)
> 
> With this patch, we are sure that nr_servers > 0. Passing the same bogus
> -smp option then leads to:
> 
> qemu-system-ppc64: Cannot support more than 8 threads on PPC with KVM
> 
> ... which is a lot more explicit than the XICS errors.
> 
> Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>

Looks sensible, thanks.

Applied to spapr-next branch.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-05-25  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 10:29 [Qemu-devel] [PATCH] spapr: ensure we have at least one XICS server Greg Kurz
2015-05-25  1:30 ` David Gibson [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=20150525013002.GG6255@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=gkurz@linux.vnet.ibm.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 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.