All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Chen Baozi <cbz@baozis.org>, Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xenproject.org, Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH V2 1/8] xen/arm64: increase MAX_VIRT_CPUS to 128 on arm64
Date: Mon, 25 May 2015 11:46:16 +0200	[thread overview]
Message-ID: <5562EF68.80007@citrix.com> (raw)
In-Reply-To: <20150525010116.GB27980@cbz-thinkpad>

Hi Chen,

On 25/05/2015 03:01, Chen Baozi wrote:
> On Sat, May 23, 2015 at 03:46:32PM +0100, Julien Grall wrote:
>> On 23/05/2015 14:52, Chen Baozi wrote:
>>> From: Chen Baozi <baozich@gmail.com>
>>>
>>> GIC-500 supports up to 128 cores in a single SoC. Increase MAX_VIRT_CPUS
>>> to 128 on arm64.
>>
>> This series have to be bisectable. Although, this patch will break
>> compilation on ARM64 because you increased MAX_VIRT_CPUS without the
>> re-distributor region (done in the next patch).
>>
>> Furthermore, GICv2 is only supporting 8 CPUs. We don't have to allow a guest
>> with more than 8 vCPUs when the GICv2 is in use.
>
> What's your suggestion? I don't think we could know whether it is built for
> a GICv2 or a GICv3 machine and define different values for corresponding
> target.

I'm not sure to understand your problem here. You know which vGIC 
version is emulated for a specific domain at domain creation time. The 
function domain_max_vcpus returns the maximum vCPUs for a give domain.

You could create a new field in vgic_v2_ops to store the maximum number 
of vCPU handled.

domain_max_vcpus would look like:

return (min(d->arch->vgic.handler.max_vcpus, MAX_VIRT_CPUS));

Regards,

-- 
-- 
Julien Grall

  reply	other threads:[~2015-05-25  9:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-23 13:52 [PATCH V2 0/8] Support more than 8 vcpus on arm64 with GICv3 Chen Baozi
2015-05-23 13:52 ` [PATCH V2 1/8] xen/arm64: increase MAX_VIRT_CPUS to 128 on arm64 Chen Baozi
2015-05-23 14:46   ` Julien Grall
2015-05-25  1:01     ` Chen Baozi
2015-05-25  9:46       ` Julien Grall [this message]
2015-05-23 13:52 ` [PATCH V2 2/8] xen/arm: gic-v3: Increase the size of GICR in address space for guest Chen Baozi
2015-05-23 14:48   ` Julien Grall
2015-05-23 13:52 ` [PATCH V2 3/8] xen/arm: Add funtions of mapping between vCPUID and vMPIDR Chen Baozi
2015-05-23 18:36   ` Julien Grall
2015-05-23 13:52 ` [PATCH V2 4/8] xen/arm: Use the new mapping relations " Chen Baozi
2015-05-24 12:51   ` Julien Grall
2015-05-25  2:34     ` Chen Baozi
2015-05-25  9:53       ` Julien Grall
2015-05-23 13:52 ` [PATCH V2 5/8] xen/arm: vGIC: Consider AFF1 when injecting SGI Chen Baozi
2015-05-26 14:36   ` Julien Grall
2015-05-23 13:52 ` [PATCH V2 6/8] tools/libxl: Make DT node of GICv3 according to max_vcpus Chen Baozi
2015-05-26 14:40   ` Julien Grall
2015-05-23 13:52 ` [PATCH V2 7/8] tools/libxl: Set logical CPUID in DT node equal to MPIDR for domU Chen Baozi
2015-05-26 14:48   ` Julien Grall
2015-05-23 13:52 ` [PATCH V2 8/8] xen/arm: Set logical CPUID in DT node for dom0 the same as MPIDR Chen Baozi
2015-05-26 14:50   ` 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=5562EF68.80007@citrix.com \
    --to=julien.grall@citrix.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.