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  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]
Date:   Wed, 30 Aug 2017 15:56:57 +0100
From:   Marc Zyngier <>
To:     Christoffer Dall <>
        Christoffer Dall <>,
        Thomas Gleixner <>,
        Jason Cooper <>,
        Eric Auger <>,
        Shanker Donthineni <>,
        Mark Rutland <>,
        Shameerali Kolothum Thodi 
Subject: Re: [PATCH v3 49/59] KVM: arm/arm64: GICv4: Propagate VLPI properties
 at map time

On 28/08/17 19:18, Christoffer Dall wrote:
> On Mon, Jul 31, 2017 at 06:26:27PM +0100, Marc Zyngier wrote:
>> When the VLPI gets mapped, it must inherit the configuration of
>> LPI configured at the vITS level. FOr that purpose, let's make
> *the LPI
> *For that

Will fix, thanks.

>> update_lpi_config globally available and call it just after
>> having performed the VLPI map operation.
> I assume this means that the GIC compares the priorities of virtual
> interrupts in the LRs with the priorities of the pending VLPIs and
> figures out what to signal first?  I couldn't find anywhere in the spec
> where this is explicitly stated.

There is this mention in IHI0069D, 5.4 (Virtual LPI support):

"The Redistributor associated with the PE on which the vPE is scheduled
determines the highest priority pending vLPI, and forwards this to the
virtual CPU interface of the vPE. This vLPI and the interrupts in the
List register are then prioritized together to determine the highest
priority pending virtual interrupt for the vPE."


Jazz is not dead. It just smells funny...

Powered by blists - more mailing lists