PING Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia > -----Original Message----- > From: kvm-owner@xxxxxxxxxxxxxxx [mailto:kvm-owner@xxxxxxxxxxxxxxx] On Behalf Of Pavel Fedin > Sent: Wednesday, August 05, 2015 1:54 PM > To: kvmarm@xxxxxxxxxxxxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx > Cc: Christoffer Dall; Marc Zyngier > Subject: [PATCH v3 0/3] KVM: arm/arm64: Allow to use KVM without in-kernel irqchip > > This patch set brings back functionality which was broken in v4.0. > Unfortunately because of restrictions of such a hardware is is impossible > to take advantage of virtual architected timer, therefore guest, running > in such restricted mode, has to use some memory-mapped timer. But it is > still better than nothing. > > v2 => v3: > - Improved commit messages, added references to commits where the respective > functionality was broken > - Explicitly specify that the solution currently affects only vGIC and has > nothing to do with timer. > - Fixed code style according to previous notes > - Removed ARM64 save/restore patch introduced in v2 because it was already > obsolete for linux-next > - Modify KVM_CAP_IRQFD handling in correct place > > v1 => v2: > - Do not use defensive approach in patch 0001. Use correct conditions in > callers instead > - Added ARM64-specific code, without which attempt to run a VM ends in a > HYP crash because of unset vGIC save/restore function pointers > > Pavel Fedin (3): > Fix NULL pointer dereference if KVM is used without in-kernel irqchip > Detect vGIC presence at runtime > Make KVM_CAP_IRQFD dependent on KVM_CAP_IRQCHIP > > arch/arm/kvm/arm.c | 19 ++++++++++++++++--- > virt/kvm/kvm_main.c | 5 +++-- > 2 files changed, 19 insertions(+), 5 deletions(-) > > -- > 2.4.4 > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
