From: Julien Grall <julien.grall@linaro.org>
To: xen-devel@lists.xen.org
Cc: patches@linaro.org, ian.campbell@citrix.com,
Julien Grall <julien.grall@linaro.org>,
stefano.stabellini@eu.citrix.com
Subject: [PATCH v5 0/7] Dissociate logical and gic/hardware CPU ID
Date: Thu, 26 Sep 2013 12:09:34 +0100 [thread overview]
Message-ID: <1380193781-17474-1-git-send-email-julien.grall@linaro.org> (raw)
Hi,
This is the fifth version of this patch series.
With the Versatile Express TC2, it's possible to boot only with A7 or A15. If
the user choose to boot with only A7, the CPU ID will start at 0x100. As Xen
relies on it to set the logical ID and the GIC, it won't be possible to use
Xen with this use case.
This patch series is divided in 3 parts:
- Patch 1: prepare Xen
- Patch 2-4: dissociate logical and gic CPU ID
- Patch 5-6: dissociate logical and hardware CPU ID
For the moment this patch series only modifies Xen and not the boot process
(ie head.S). So if the boot CPU ID is not equal to 0 you won't be able to start
Xen. The future Ian Campbel's patch series should resolve this issue.
The major changes are:
- Introduce init_info structure to gather all CPU boot informations
All changes can be found in each patch.
Cheers,
Julien Grall (7):
xen/arm: Introduce init_info structure
xen/arm: use cpumask_t to describe cpu mask in gic_route_dt_irq
xen/arm: Initialize correctly IRQ routing
xen/arm: gic: Use the correct CPU ID
xen/arm: Fix assert in send_SGI_one
xen/arm: Dissociate logical and hardware CPU ID
xen/arm: Use the hardware ID to boot correctly secondary cpus
xen/arch/arm/arm32/asm-offsets.c | 4 ++
xen/arch/arm/arm32/head.S | 3 +-
xen/arch/arm/arm64/asm-offsets.c | 3 +
xen/arch/arm/arm64/head.S | 3 +-
xen/arch/arm/gic.c | 64 +++++++++++++++++-----
xen/arch/arm/setup.c | 112 +++++++++++++++++++++++++++++++++++++-
xen/arch/arm/smpboot.c | 26 ++++++---
xen/arch/arm/time.c | 6 +-
xen/common/device_tree.c | 48 ----------------
xen/include/asm-arm/gic.h | 3 +-
xen/include/asm-arm/init.h | 8 +++
xen/include/asm-arm/processor.h | 4 ++
12 files changed, 206 insertions(+), 78 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-09-26 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 11:09 Julien Grall [this message]
2013-09-26 11:09 ` [PATCH v5 1/7] xen/arm: Introduce init_info structure Julien Grall
2013-09-26 11:09 ` [PATCH v5 2/7] xen/arm: use cpumask_t to describe cpu mask in gic_route_dt_irq Julien Grall
2013-09-26 11:09 ` [PATCH v5 3/7] xen/arm: Initialize correctly IRQ routing Julien Grall
2013-09-26 11:09 ` [PATCH v5 4/7] xen/arm: gic: Use the correct CPU ID Julien Grall
2013-09-26 11:09 ` [PATCH v5 5/7] xen/arm: Fix assert in send_SGI_one Julien Grall
2013-09-26 11:09 ` [PATCH v5 6/7] xen/arm: Dissociate logical and hardware CPU ID Julien Grall
2013-09-26 11:09 ` [PATCH v5 7/7] xen/arm: Use the hardware ID to boot correctly secondary cpus Julien Grall
2013-09-26 15:09 ` [PATCH v5 0/7] Dissociate logical and gic/hardware CPU ID Ian Campbell
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=1380193781-17474-1-git-send-email-julien.grall@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 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).