[lkml]   [2020]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v7 5/7] KVM: arm64: pmu: Make overflow handler NMI safe
Hi Will,

On 9/28/20 6:57 PM, Will Deacon wrote:

> On Thu, Sep 24, 2020 at 12:07:04PM +0100, Alexandru Elisei wrote:
>> From: Julien Thierry <>
>> kvm_vcpu_kick() is not NMI safe. When the overflow handler is called from
>> NMI context, defer waking the vcpu to an irq_work queue.
>> A vcpu can be freed while it's not running by kvm_destroy_vm(). Prevent
>> running the irq_work for a non-existent vcpu by calling irq_work_sync() on
>> the PMU destroy path.
>> Cc: Julien Thierry <>
>> Cc: Marc Zyngier <>
>> Cc: Will Deacon <>
>> Cc: Mark Rutland <>
>> Cc: Catalin Marinas <>
>> Cc: James Morse <>
>> Cc: Suzuki K Pouloze <>
>> Cc:
>> Cc:
>> Signed-off-by: Julien Thierry <>
>> Tested-by: Sumit Garg <> (Developerbox)
>> [Alexandru E.: Added irq_work_sync()]
>> Signed-off-by: Alexandru Elisei <>
>> ---
>> I suggested in v6 that I will add an irq_work_sync() to
>> kvm_pmu_vcpu_reset(). It turns out it's not necessary: a vcpu reset is done
>> by the vcpu being reset with interrupts enabled, which means all the work
>> has had a chance to run before the reset takes place.
> I don't understand this ^^

Marc had the same comment, I replied in his email. I thought about it and you're
right, it doesn't make much sense.

> But the patch itself looks good, so I'm going to queue this lot anyway!

Thank you for picking up the series!


 \ /
  Last update: 2020-09-30 14:37    [W:0.488 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site