From: Julien Grall <julien.grall@citrix.com>
To: Chen Baozi <cbz@baozis.org>, xen-devel@lists.xenproject.org
Cc: julien.grall@citrix.com, Chen Baozi <baozich@gmail.com>,
ian.campbell@citrix.com
Subject: Re: [RFC 2/4] xen/arm64: increase MAX_VIRT_CPUS to 128 on arm64
Date: Thu, 14 May 2015 18:55:29 +0100 [thread overview]
Message-ID: <5554E191.5030303@citrix.com> (raw)
In-Reply-To: <1431612863-3762-3-git-send-email-cbz@baozis.org>
Hi Chen,
On 14/05/15 15:14, Chen Baozi wrote:
> From: Chen Baozi <baozich@gmail.com>
>
> GIC-500 supports up to 128 cores in a single SoC. Since the
> redistributor register map is no longer set by fixed size, which limits
> the number of vcpu, we increase MAX_VIRT_CPUS to 128 and remove the
> corresponding restriction.
>
> Signed-off-by: Chen Baozi <baozich@gmail.com>
> ---
> xen/arch/arm/vgic-v3.c | 3 ---
> xen/include/asm-arm/config.h | 4 ++++
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm/vgic-v3.c
> index a0c1de9..83e7344 100644
> --- a/xen/arch/arm/vgic-v3.c
> +++ b/xen/arch/arm/vgic-v3.c
> @@ -906,7 +906,6 @@ static int vgic_v3_distr_mmio_write(struct vcpu *v, mmio_info_t *info)
> rank = vgic_rank_offset(v, 64, gicd_reg - GICD_IROUTER,
> DABT_DOUBLE_WORD);
> if ( rank == NULL ) goto write_ignore;
> - BUG_ON(v->domain->max_vcpus > 8);
This was here to catch bump of MAX_VIRT without adapting the vGIC code.
The current vGICv3 is not supporting more than 16 vCPUs because it only
cares about AFF0.
> new_irouter = *r;
> vgic_lock_rank(v, rank, flags);
>
> @@ -1203,8 +1202,6 @@ static int vgic_v3_domain_init(struct domain *d)
> d->arch.vgic.nr_regions = GUEST_GICV3_RDIST_REGIONS;
> d->arch.vgic.rdist_stride = GUEST_GICV3_RDIST_STRIDE;
>
> - /* The first redistributor should contain enough space for all CPUs */
> - BUILD_BUG_ON((GUEST_GICV3_GICR0_SIZE / GUEST_GICV3_RDIST_STRIDE) < MAX_VIRT_CPUS);
I'd like to keep this BUILD_BUG_ON. It ensures that we reserved enough
space in the guest layout for the redistributors.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-05-14 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 14:14 [RFC 0/4] Support more than 8 vcpus on arm64 with GICv3 Chen Baozi
2015-05-14 14:14 ` [RFC 1/4] xen/arm64: Map the redistributor region by max_vcpus of domU danamically Chen Baozi
2015-05-14 17:51 ` Julien Grall
2015-05-14 14:14 ` [RFC 2/4] xen/arm64: increase MAX_VIRT_CPUS to 128 on arm64 Chen Baozi
2015-05-14 17:55 ` Julien Grall [this message]
2015-05-14 14:14 ` [RFC 3/4] tools/libxl: Make DT node of GICv3 according to max_vcpus Chen Baozi
2015-05-14 14:14 ` [RFC 4/4] xen/arm: Remove unnecessary GUEST_GICV3_GICR0_SIZE macro Chen Baozi
2015-05-14 18:03 ` Julien Grall
2015-05-14 17:48 ` [RFC 0/4] Support more than 8 vcpus on arm64 with GICv3 Julien Grall
2015-05-14 18:04 ` Julien Grall
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=5554E191.5030303@citrix.com \
--to=julien.grall@citrix.com \
--cc=baozich@gmail.com \
--cc=cbz@baozis.org \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.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.