linux-kernel - RE: [PATCH 6/7] irqchip/gic-v3-its: Honor hypervisor enforced LPI range

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5FC3163CFD30C246ABAA99954A238FA838706A1B@FRAEML521-MBX.china.huawei.com>
Date:   Fri, 22 Jun 2018 16:31:40 +0000
From:   Shameerali Kolothum Thodi <shameerali.kolothum.thodi@...wei.com>
To:     Marc Zyngier <marc.zyngier@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     Thomas Gleixner <tglx@...utronix.de>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        Shanker Donthineni <shankerd@...eaurora.org>,
        Laurentiu Tudor <laurentiu.tudor@....com>,
        Lei Zhang <zhang.lei@...fujitsu.com>,
        Linuxarm <linuxarm@...wei.com>
Subject: RE: [PATCH 6/7] irqchip/gic-v3-its: Honor hypervisor enforced LPI
 range

Hi Marc,

> -----Original Message-----
> From: Marc Zyngier [mailto:marc.zyngier@....com]
> Sent: 20 June 2018 14:53
> To: linux-kernel@...r.kernel.org
> Cc: Thomas Gleixner <tglx@...utronix.de>; Ard Biesheuvel
> <ard.biesheuvel@...aro.org>; Shanker Donthineni
> <shankerd@...eaurora.org>; Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@...wei.com>; MaJun <majun258@...wei.com>;
> Laurentiu Tudor <laurentiu.tudor@....com>; Lei Zhang
> <zhang.lei@...fujitsu.com>
> Subject: [PATCH 6/7] irqchip/gic-v3-its: Honor hypervisor enforced LPI range
> 
> A recent extension to the GIC architecture allows a hypervisor to
> arbitrarily reduce the number of LPIs available to a guest, no
> matter what the GIC says about the valid range of IntIDs.
> 
> Let's factor in this information when computing the number of
> available LPIs

On our D05 board, this limits the lpis to 2 and results in MSI irq alloc fails:

[    0.000000] ITS: Using hypervisor restricted LPI range [2]
....
[   10.543889] ixgbe 000a:11:00.1: Failed to allocate MSI interrupt, falling back to legacy. Error: -12
 
> Signed-off-by: Marc Zyngier <marc.zyngier@....com>
> ---
>  drivers/irqchip/irq-gic-v3-its.c   | 9 +++++++++
>  include/linux/irqchip/arm-gic-v3.h | 1 +
>  2 files changed, 10 insertions(+)
> 
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index 8c7e8c235faf..903ca1c19553 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -1525,8 +1525,17 @@ static int free_lpi_range(u32 base, u32 nr_lpis)
>  static int __init its_lpi_init(u32 id_bits)
>  {
>  	u32 lpis = (1UL << id_bits) - 8192;
> +	u32 numlpis;
>  	int err;
> 
> +	numlpis = 1UL << GICD_TYPER_NUM_LPIS(gic_rdists->gicd_typer);
> +
> +	if (numlpis > 1 && !WARN_ON(numlpis > lpis)) {
> +		lpis = numlpis;
> +		pr_info("ITS: Using hypervisor restricted LPI range [%u]\n",
> +			lpis);
> +	}

I don't have the GICv3 extension doc, but did you intent to check for,

 if (numlpis > 2 && !WARN_ON(numlpis > lpis)) {

as it looks like D05 returns 0 for bits 11-15 and that makes numlpis=2.

Please let me know.

Thanks,
Shameer

> +
>  	/*
>  	 * Initializing the allocator is just the same as freeing the
>  	 * full range of LPIs.
> diff --git a/include/linux/irqchip/arm-gic-v3.h b/include/linux/irqchip/arm-gic-
> v3.h
> index 396cd99af02f..9d2ea3e907d0 100644
> --- a/include/linux/irqchip/arm-gic-v3.h
> +++ b/include/linux/irqchip/arm-gic-v3.h
> @@ -73,6 +73,7 @@
>  #define GICD_TYPER_MBIS			(1U << 16)
> 
>  #define GICD_TYPER_ID_BITS(typer)	((((typer) >> 19) & 0x1f) + 1)
> +#define GICD_TYPER_NUM_LPIS(typer)	((((typer) >> 11) & 0x1f) + 1)
>  #define GICD_TYPER_IRQS(typer)		((((typer) & 0x1f) + 1) * 32)
> 
>  #define GICD_IROUTER_SPI_MODE_ONE	(0U << 31)
> --
> 2.17.1