[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XEN v2 12/12] xen/Arm: GICv3: Enable GICv3 for AArch32


  • To: Ayan Kumar Halder <ayankuma@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Michal Orzel <michal.orzel@xxxxxxx>
  • Date: Fri, 4 Nov 2022 10:55:25 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=QMiYgNQoHDDCi76G1G6p2oh/+q8mXH1uYqpKiFOWwqU=; b=TBZJTYRiax+hE3C6IGCcMlJKTddJ9dY9yE62b6rePWMX6JqG1CURz+XEN0aMfGNEwRX230Nmj901FrHJi6wRRl08UQN0yM3tCGHN+v9US94IVbxw2F//wqd8V9UmvIzQW9Ua+qX70+oKg0t6rm7Ky64MA2bHjJRbh6MlVKYrQmxqBEWQUtPSUdR6xabMuxJA7to1ieAq8m5ofONfRJez6ooReL82V/OfZ4owyU5BOMpL4lSFIJSr3LNSDwADXFjWou1pslFPf0guZEzguXXHrSMwXYXv4WW2kI9jB2cI2WI9y4KE++4agBf5oAwdv5NXywQxHY1Ds5xrlge3Kz3g7g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GsE0fhk5LJUQ68ziXXwVXbnnXNDOEaDmBaZ/ZtpLGaLHZ1Wbx09t2w7l9vRo5Na76dxewilm/4qkNvkpBIT/DDYvreasz8IuHQhDnZOi+5CSdo9xBviiYRWwQIZ+A/Jl9q6vwRrAmH093jSvU8rFni850SDmvoa4v9keIegC0Lnl6QTJl9mcVseg7WgC0qjMOkNTd1B2mgrYm5jc1dFk73h+rvTkKqeD12Sl61UCpqAa4tBOUn7NLj5eJtszZgSw9bHk8s0UZSzxDi/YiErVjQmC3G+/X2eBx4S+8kP+FmCKK8FyC7pXHFiZsCj3MnRBZnVtfLQ3+rInU3rilTB4Bg==
  • Cc: <sstabellini@xxxxxxxxxx>, <stefanos@xxxxxxxxxx>, <julien@xxxxxxx>, <Volodymyr_Babchuk@xxxxxxxx>, <bertrand.marquis@xxxxxxx>, <burzalodowa@xxxxxxxxx>
  • Delivery-date: Fri, 04 Nov 2022 09:55:39 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hi Ayan,

On 31/10/2022 16:13, Ayan Kumar Halder wrote:
> 
> 
> Refer ARM DDI 0487G.b ID072021,
> D13.2.86 -
> ID_PFR1_EL1, AArch32 Processor Feature Register 1
> 
> GIC, bits[31:28] == 0b0001 for GIC3.0 on Aarch32
> 
> One can now enable GICv3 on AArch32 systems. However, ITS is not supported.
> The reason being currently we are trying to validate GICv3 on an AArch32_v8R
> system. Refer ARM DDI 0568A.c ID110520, B1.3.1,
> "A Generic Interrupt Controller (GIC) implemented with an Armv8-R PE must not
> implement LPI support."
> 
> Updated SUPPORT.md.
> 
> Signed-off-by: Ayan Kumar Halder <ayankuma@xxxxxxx>
> ---
> 
> Changed from :-
> v1 - 1. Remove "ARM_64 || ARM_32" as it is always true.
> 2. Updated SUPPORT.md.
> 
>  SUPPORT.md                            | 6 ++++++
>  xen/arch/arm/Kconfig                  | 4 ++--
>  xen/arch/arm/include/asm/cpufeature.h | 1 +
>  3 files changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/SUPPORT.md b/SUPPORT.md
> index cf2ddfacaf..0137855c66 100644
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -82,6 +82,12 @@ Extension to the GICv3 interrupt controller to support MSI.
> 
>      Status: Experimental
> 
> +### ARM/GICv3 + AArch32 ARM v8
> +
> +GICv3 is supported on AArch32 ARMv8 (besides AArch64)
Looking at the CONFIG_GICV3, it can be enabled on arm32, which at the moment
supports only ARMv7 (see __lookup_processor_type -> proc-v7.S).
What will prevent the user from enabling GICv3 for ARMv7 based CPU?

> +
> +    Status: Supported, not security supported
> +
>  ## Guest Type
> 
>  ### x86/PV
> diff --git a/xen/arch/arm/Kconfig b/xen/arch/arm/Kconfig
> index 1fe5faf847..7c3c6eb3bd 100644
> --- a/xen/arch/arm/Kconfig
> +++ b/xen/arch/arm/Kconfig
> @@ -41,7 +41,7 @@ config ARM_EFI
> 
>  config GICV3
>         bool "GICv3 driver"
> -       depends on ARM_64 && !NEW_VGIC
> +       depends on !NEW_VGIC
>         default y
>         ---help---
> 
> @@ -50,7 +50,7 @@ config GICV3
> 
>  config HAS_ITS
>          bool "GICv3 ITS MSI controller support (UNSUPPORTED)" if UNSUPPORTED
> -        depends on GICV3 && !NEW_VGIC
> +        depends on GICV3 && !NEW_VGIC && !ARM_32
> 
>  config HVM
>          def_bool y
> diff --git a/xen/arch/arm/include/asm/cpufeature.h 
> b/xen/arch/arm/include/asm/cpufeature.h
> index c86a2e7f29..c62cf6293f 100644
> --- a/xen/arch/arm/include/asm/cpufeature.h
> +++ b/xen/arch/arm/include/asm/cpufeature.h
> @@ -33,6 +33,7 @@
>  #define cpu_has_aarch32   (cpu_has_arm || cpu_has_thumb)
> 
>  #ifdef CONFIG_ARM_32
> +#define cpu_has_gicv3     (boot_cpu_feature32(gic) >= 1)
What is the purpose of defining this macro if it is not used?

>  #define cpu_has_gentimer  (boot_cpu_feature32(gentimer) == 1)
>  /*
>   * On Armv7, the value 0 is used to indicate that PMUv2 is not
> --
> 2.17.1
> 
> 
~Michal



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.