[Xen-devel] [PATCH v5 0/7] Dissociate logical and gic/hardware CPU ID

[Julien Grall <julien.grall@xxxxxxxxxx>]

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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel