From: Julien Grall <julien.grall@linaro.org>
To: Julien Grall <julien.grall@linaro.org>
Cc: stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
patches@linaro.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v3 3/6] xen/arm: gic: Use the correct CPU ID
Date: Fri, 20 Sep 2013 13:44:43 +0100 [thread overview]
Message-ID: <523C433B.7030404@linaro.org> (raw)
In-Reply-To: <1379510122-9467-4-git-send-email-julien.grall@linaro.org>
On 09/18/2013 02:15 PM, Julien Grall wrote:
> The GIC mapping of CPU interfaces does not necessarily match the logical
> CPU numbering.
>
> When Xen wants to send an SGI to specific CPU, it needs to use the GIC CPU ID.
> It can be retrieved from ITARGETSR0, in fact when this field is read, the GIC
> will return a value that corresponds only to the processor reading the register.
> So Xen can use the PPI 0 to initialize the mapping.
>
> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>
> ---
> Changes in v3:
> - Correctly create the mask in gic_cpu_mask
>
> Changes in v2:
> - Use per-cpu variable instead of an array
> - Add comment for NR_GIC_CPU_IF
> ---
> xen/arch/arm/gic.c | 37 ++++++++++++++++++++++++++++++-------
> 1 file changed, 30 insertions(+), 7 deletions(-)
>
> diff --git a/xen/arch/arm/gic.c b/xen/arch/arm/gic.c
> index b969d23..4061691 100644
> --- a/xen/arch/arm/gic.c
> +++ b/xen/arch/arm/gic.c
> @@ -57,6 +57,29 @@ static DEFINE_PER_CPU(uint64_t, lr_mask);
>
> static unsigned nr_lrs;
>
> +/* The GIC mapping of CPU interfaces does not necessarily match the
> + * logical CPU numbering. Let's use mapping as returned by the GIC
> + * itself
> + */
> +static DEFINE_PER_CPU(u8, gic_cpu_id);
> +
Following the discussion on another thread
(http://lists.xen.org/archives/html/xen-devel/2013-09/msg02072.html), we
need to initialize each CPU ID to 0xff by default, to be able to bring
up secondary CPUs with an SGI (send_SGI_mask).
But as I understand, per_cpu area for a give area is initialized in
cpu_up and there is no way to give a default value. So user could call
send_SGI_mask to early function and use an invalid CPU area.
IMHO, this solution is too fragile and I would like to use the same
solution as my first version (ie with an array of 8 cells).
Ian, is ok for you?
> +/* Maximum cpu interface per GIC */
> +#define NR_GIC_CPU_IF 8
> +
> +static unsigned int gic_cpu_mask(const cpumask_t *cpumask)
> +{
> + unsigned int cpu;
> + unsigned int mask = 0;
> +
> + for_each_cpu(cpu, cpumask)
> + {
> + ASSERT(cpu < NR_GIC_CPU_IF);
> + mask |= per_cpu(gic_cpu_id, cpu);
> + }
> +
> + return mask;
> +}
> +
> unsigned int gic_number_lines(void)
> {
> return gic.lines;
> @@ -189,9 +212,7 @@ static void gic_set_irq_properties(unsigned int irq, bool_t level,
> {
> volatile unsigned char *bytereg;
> uint32_t cfg, edgebit;
> - unsigned int mask = cpumask_bits(cpu_mask)[0];
> -
> - ASSERT(!(mask & ~0xff)); /* Target bitmap only support 8 CPUS */
> + unsigned int mask = gic_cpu_mask(cpu_mask);
>
> /* Set edge / level */
> cfg = GICD[GICD_ICFGR + irq / 16];
> @@ -300,6 +321,8 @@ static void __cpuinit gic_cpu_init(void)
> {
> int i;
>
> + this_cpu(gic_cpu_id) = GICD[GICD_ITARGETSR] & 0xff;
> +
> /* The first 32 interrupts (PPI and SGI) are banked per-cpu, so
> * even though they are controlled with GICD registers, they must
> * be set up here with the other per-cpu state. */
> @@ -431,13 +454,13 @@ void __init gic_init(void)
>
> void send_SGI_mask(const cpumask_t *cpumask, enum gic_sgi sgi)
> {
> - unsigned long mask = cpumask_bits(cpumask)[0];
> + cpumask_t online_mask;
> + unsigned int mask = 0;
>
> ASSERT(sgi < 16); /* There are only 16 SGIs */
>
> - mask &= cpumask_bits(&cpu_online_map)[0];
> -
> - ASSERT(mask < 0x100); /* The target bitmap only supports 8 CPUs */
> + cpumask_and(&online_mask, cpumask, &cpu_online_map);
> + mask = gic_cpu_mask(&online_mask);
>
> dsb();
>
>
--
Julien Grall
next prev parent reply other threads:[~2013-09-20 12:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 13:15 [PATCH v3 0/6] Dissociate logical and gic/hardware CPU ID Julien Grall
2013-09-18 13:15 ` [PATCH v3 1/6] xen/arm: use cpumask_t to describe cpu mask in gic_route_dt_irq Julien Grall
2013-09-25 15:36 ` Ian Campbell
2013-09-18 13:15 ` [PATCH v3 2/6] xen/arm: Initialize correctly IRQ routing Julien Grall
2013-09-25 15:37 ` Ian Campbell
2013-09-18 13:15 ` [PATCH v3 3/6] xen/arm: gic: Use the correct CPU ID Julien Grall
2013-09-20 12:44 ` Julien Grall [this message]
2013-09-20 13:36 ` Ian Campbell
2013-09-20 13:49 ` Julien Grall
2013-09-20 15:03 ` Julien Grall
2013-09-20 15:44 ` Ian Campbell
2013-09-20 15:58 ` Julien Grall
2013-09-20 16:06 ` Ian Campbell
2013-09-20 18:48 ` Julien Grall
2013-09-25 15:35 ` Ian Campbell
2013-09-25 15:42 ` Julien Grall
2013-09-25 15:48 ` Ian Campbell
2013-09-25 15:53 ` Ian Campbell
2013-09-25 16:34 ` Tim Deegan
2013-09-18 13:15 ` [PATCH v3 4/6] xen/arm: Fix assert in send_SGI_one Julien Grall
2013-09-25 15:37 ` Ian Campbell
2013-09-18 13:15 ` [PATCH v3 5/6] xen/arm: Dissociate logical and hardware CPU ID Julien Grall
2013-09-25 15:38 ` Ian Campbell
2013-09-18 13:15 ` [PATCH v3 6/6] xen/arm: Use the hardware ID to boot correctly secondary cpus Julien Grall
2013-09-25 15:41 ` Ian Campbell
2013-09-26 10:18 ` 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=523C433B.7030404@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=patches@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.