From: Igor Mammedov <imammedo@redhat.com>
To: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
David Woodhouse <dwmw@amazon.co.uk>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
Peter Maydell <peter.maydell@linaro.org>,
"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>
Subject: Re: [PATCH v2 5/6] xen_arm: Set mc->max_cpus to GUEST_MAX_VCPUS in xen_arm_init()
Date: Fri, 24 Nov 2023 13:04:34 +0100 [thread overview]
Message-ID: <20231124130434.057951b6@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20231121221023.419901-6-volodymyr_babchuk@epam.com>
On Tue, 21 Nov 2023 22:10:28 +0000
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com> wrote:
Probably typo in 'subj'
mc->max_cpus
is limit on maximum supported vCPUs and it shouldn't be set
by xen_arm_init()
patch itself though does the right thing by setting it
in xen_arm_machine_class_init()
Also below explanation, while valid is not the reason for
increasing mc->max_cpus.
Reason could be as simple as
'increase max vCPU limit for FOO machine to XXX'
otherwise machine creation would be aborted early by generic code
with error '...'
see machine_parse_smp_config()
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
> The number of vCPUs used for the IOREQ configuration (machine->smp.cpus)
> should really match the system value as for each vCPU we setup a dedicated
> evtchn for the communication with Xen at the runtime. This is needed
> for the IOREQ to be properly configured and work if the involved domain
> has more than one vCPU assigned.
>
> Set the number of current supported guest vCPUs here (128) which is
> defined in public header arch-arm.h. And the toolstack should then
> pass max_vcpus using "-smp" arg.
>
> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
> ---
> hw/arm/xen_arm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/arm/xen_arm.c b/hw/arm/xen_arm.c
> index a5631529d0..b9c3ae14b6 100644
> --- a/hw/arm/xen_arm.c
> +++ b/hw/arm/xen_arm.c
> @@ -231,7 +231,7 @@ static void xen_arm_machine_class_init(ObjectClass *oc, void *data)
> MachineClass *mc = MACHINE_CLASS(oc);
> mc->desc = "Xen Para-virtualized PC";
> mc->init = xen_arm_init;
> - mc->max_cpus = 1;
> + mc->max_cpus = GUEST_MAX_VCPUS;
> mc->default_machine_opts = "accel=xen";
> /* Set explicitly here to make sure that real ram_size is passed */
> mc->default_ram_size = 0;
prev parent reply other threads:[~2023-11-24 12:05 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 22:10 [PATCH v2 0/6] xen-arm: add support for virtio-pci Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it Volodymyr Babchuk
2023-11-22 15:54 ` Paul Durrant
2023-11-22 17:05 ` Paul Durrant
2023-11-22 22:44 ` Woodhouse, David via
2023-11-22 23:49 ` Volodymyr Babchuk
2023-11-22 23:55 ` Woodhouse, David via
2023-11-22 22:56 ` Volodymyr Babchuk
2023-11-22 23:04 ` David Woodhouse
2023-11-23 9:29 ` Paul Durrant
2023-11-21 22:10 ` [PATCH v2 3/6] xen: xenstore: add possibility to preserve owner Volodymyr Babchuk
2023-11-22 17:07 ` Paul Durrant
2023-11-22 22:28 ` Stefano Stabellini
2023-11-22 23:01 ` David Woodhouse
2023-11-22 23:03 ` Volodymyr Babchuk
2023-11-23 1:19 ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 2/6] xen: backends: touch some XenStore nodes only if device Volodymyr Babchuk
2023-11-22 11:07 ` Philippe Mathieu-Daudé
2023-11-22 22:49 ` Volodymyr Babchuk
2023-11-22 23:19 ` David Woodhouse
2023-11-22 17:03 ` Paul Durrant
2023-11-22 22:46 ` Woodhouse, David via
2023-11-22 22:50 ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 4/6] xen_pvdev: Do not assume Dom0 when creating a directory Volodymyr Babchuk
2023-11-22 17:11 ` Paul Durrant
2023-11-22 22:29 ` Stefano Stabellini
2023-11-22 23:03 ` David Woodhouse
2023-11-22 23:09 ` Stefano Stabellini
2023-11-22 23:11 ` David Woodhouse
2023-11-22 23:20 ` Stefano Stabellini
2023-11-22 23:46 ` Volodymyr Babchuk
2023-11-23 0:07 ` Volodymyr Babchuk
2023-11-23 9:28 ` Paul Durrant
2023-11-23 10:45 ` David Woodhouse
2023-11-23 11:43 ` Volodymyr Babchuk
2023-11-23 11:51 ` David Woodhouse
2023-11-23 11:54 ` Volodymyr Babchuk
2023-11-23 11:57 ` David Woodhouse
2023-11-23 12:17 ` Volodymyr Babchuk
2023-11-23 12:27 ` David Woodhouse
2023-11-23 12:54 ` Paul Durrant
2023-11-24 0:24 ` Volodymyr Babchuk
2023-11-24 12:56 ` Alex Bennée
2023-11-21 22:10 ` [PATCH v2 6/6] xen_arm: Add virtual PCIe host bridge support Volodymyr Babchuk
2023-11-22 22:39 ` Stefano Stabellini
2023-11-22 23:44 ` Vikram Garhwal
2023-11-23 0:11 ` Volodymyr Babchuk
2023-11-24 12:30 ` Igor Mammedov
2023-11-24 15:47 ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 5/6] xen_arm: Set mc->max_cpus to GUEST_MAX_VCPUS in xen_arm_init() Volodymyr Babchuk
2023-11-22 11:10 ` Philippe Mathieu-Daudé
2023-11-24 12:04 ` Igor Mammedov [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=20231124130434.057951b6@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=dwmw@amazon.co.uk \
--cc=julien@xen.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).