On 05/06/15 17:26, Ian Campbell wrote: > On Mon, 2015-06-01 at 20:56 +0800, Chen Baozi wrote: >> [...] >> +#define GICV2_MAX_CPUS 8 > > This and GICV3_MAX_CPUS don't seem very worthwhile, unless there are to > be other uses of them. > > In fact, GICV3_MAX_CPUS is really MAX_VIRT_CPUS, through it's > association with the affinity mapping, i.e. if one changes so would the > other, in lockstep. So I think you should just use that for v3 and > hardcode 8 inline for v2 (since it cannot change).
Technically the vGICv3 driver is supporting 4096 CPUs and the restriction is only because of other part of the Xen. This restriction may be removed by passing AFF1 and the target directly to the vgic_send_sgi as you suggested ealier. Regards, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
