From: "Emilio G. Cota" <cota@braap.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>,
Thomas Huth <thuth@redhat.com>,
qemu-arm@nongnu.org, Igor Mitsyanko <i.mitsyanko@gmail.com>,
Alistair Francis <alistair.francis@xilinx.com>,
"Edgar E . Iglesias" <edgar.iglesias@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw: add .min_cpus and .default_cpus fields to machine_class
Date: Fri, 3 Nov 2017 14:56:10 -0400 [thread overview]
Message-ID: <20171103185610.GA3907@flamenco> (raw)
In-Reply-To: <1509734853-3014-1-git-send-email-cota@braap.org>
On Fri, Nov 03, 2017 at 14:47:33 -0400, Emilio G. Cota wrote:
> diff --git a/hw/arm/xlnx-zcu102.c b/hw/arm/xlnx-zcu102.c
> index e2d15a1..395d1b5 100644
> --- a/hw/arm/xlnx-zcu102.c
> +++ b/hw/arm/xlnx-zcu102.c
> @@ -185,6 +185,9 @@ static void xlnx_ep108_machine_class_init(ObjectClass *oc, void *data)
> mc->block_default_type = IF_IDE;
> mc->units_per_default_bus = 1;
> mc->ignore_memory_transaction_failures = true;
> + mc->max_cpus = XLNX_ZYNQMP_NUM_APU_CPUS + XLNX_ZYNQMP_NUM_RPU_CPUS;
> + mc->min_cpus = XLNX_ZYNQMP_NUM_APU_CPUS;
> + mc->default_cpus = XLNX_ZYNQMP_NUM_APU_CPUS;
> }
>
> static const TypeInfo xlnx_ep108_machine_init_typeinfo = {
> @@ -241,6 +244,8 @@ static void xlnx_zcu102_machine_class_init(ObjectClass *oc, void *data)
> mc->units_per_default_bus = 1;
> mc->ignore_memory_transaction_failures = true;
> mc->max_cpus = XLNX_ZYNQMP_NUM_APU_CPUS + XLNX_ZYNQMP_NUM_RPU_CPUS;
> + mc->min_cpus = XLNX_ZYNQMP_NUM_APU_CPUS;
> + mc->default_cpus = XLNX_ZYNQMP_NUM_APU_CPUS;
> }
Should we update max_cpus to just NUM_APU_CPUS as well for these boards?
-smp 5 or 6 (NUM_APU + NUM_RPU) still gets us 4 vCPUs.
I see there's code for RPU cpus but it seems disabled at compile-time
at xlnx-zynqmp.c:431:
DEFINE_PROP_BOOL("has_rpu", XlnxZynqMPState, has_rpu, false)
Or is there a run-time way to override this?
Thanks,
Emilio
next prev parent reply other threads:[~2017-11-03 18:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 18:47 [Qemu-devel] [PATCH] hw: add .min_cpus and .default_cpus fields to machine_class Emilio G. Cota
2017-11-03 18:56 ` Emilio G. Cota [this message]
2017-11-03 20:02 ` Eduardo Habkost
2017-11-03 22:24 ` Emilio G. Cota
2017-11-06 14:10 ` Eduardo Habkost
2017-11-06 20:13 ` Emilio G. Cota
2017-11-07 0:43 ` Alistair Francis
2017-11-07 12:31 ` Eduardo Habkost
2017-11-08 21:29 ` Richard Henderson
2017-11-08 21:52 ` Eduardo Habkost
2017-11-08 22:08 ` Alistair Francis
2017-11-06 21:54 ` Emilio G. Cota
2017-11-06 22:32 ` Alistair Francis
2017-11-06 23:21 ` Emilio G. Cota
2017-11-06 23:33 ` Alistair Francis
2017-11-07 0:54 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2017-11-07 1:19 ` Alistair Francis
2017-11-07 16:15 ` Philippe Mathieu-Daudé
2017-11-07 19:32 ` [Qemu-devel] " Eduardo Habkost
2017-11-07 19:48 ` Alistair Francis
2017-11-07 19:54 ` Eduardo Habkost
2017-11-07 20:15 ` Eduardo Habkost
2017-11-10 19:23 ` Emilio G. Cota
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=20171103185610.GA3907@flamenco \
--to=cota@braap.org \
--cc=alistair.francis@xilinx.com \
--cc=edgar.iglesias@gmail.com \
--cc=ehabkost@redhat.com \
--cc=i.mitsyanko@gmail.com \
--cc=marcel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).