[PATCH 00/13] arm64: KVM: GICv3 ITS emulation
marc.zyngier at arm.com
Mon Jun 8 10:13:58 PDT 2015
On 08/06/15 11:54, Pavel Fedin wrote:
>> I'm afraid this is not enough. A write to GICR_TRANSLATER (DID+EID)
>> results in a (LPI,CPU) pair. Can you easily express the CPU part in
>> irqfd (this is a genuine question, I'm not familiar enough with that
>> part of the core)?
> But... As far as i could understand, LPI is added to a collection as a part of setup. And
> collection actually represents a destination CPU, doesn't it? And we can't have multiple
> LPIs sharing the same number and going to different CPUs. Or am i wrong? Unfortunately i
> don't have GICv3 arch reference manual.
This is true to some extent. But the point is that the result of the
translation is both an LPI and a CPU. My question was how you would
indicate convey the notion of a target vcpu when using irqfd. As far as
I know this doesn't really fit, unless we start introducing the dreaded
Do we really want to go down that road?
>> Another concern
>> would be the support of GICv4, which relies on the command queue
>> handling to be handled in the kernel
> Wow, i didn't know about GICv4.
I wish I didn't know about it.
Jazz is not dead. It just smells funny...
More information about the linux-arm-kernel