All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	Christoffer Dall <christoffer.dall@arm.com>,
	Andre Przywara <andre.przywara@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Eric Auger <eric.auger@redhat.com>,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: arm/arm64: Fix locking issues
Date: Tue, 15 May 2018 14:05:38 +0200	[thread overview]
Message-ID: <e33bdec4-97d9-fcc1-da1f-2c6d87b2c56d@redhat.com> (raw)
In-Reply-To: <b8aae9d6-1413-157d-52c2-e06511975e11@arm.com>

On 15/05/2018 13:54, Marc Zyngier wrote:
> On 15/05/18 12:35, Paolo Bonzini wrote:
>> On 15/05/2018 12:26, Christoffer Dall wrote:
>>> On Fri, May 11, 2018 at 03:20:11PM +0100, Andre Przywara wrote:
>>>> Jan recently reported lockdep complaints regarding various locks in our
>>>> VGIC emulation [1][2].
>>>> This boiled down to two separate issues:
>>>> - When promoting the vgic_irq->irq_lock to require IRQs being disabled,
>>>>   we forgot to amend some instances of this lock on the way. Also this
>>>>   needs to be applied to dependent locks as well. The first two patches
>>>>   fix that. The patch split is designed to simplify backporting.
>>>>   Those patches have been posted before, I am resending them as part
>>>>   of this series.
>>>> - Calling kvm_read_guest() requires us to be inside an SRCU critical
>>>>   section. On some architectures we are always in it when handling VCPU
>>>>   exits, but on ARM we need to lock it individually. Patches 3 and 4
>>>>   fix that, the split is again made to ease backporting.
>>>>   Each of the hunks fix an indiviual commit, but I refrained from
>>>>   splitting this down into eight patches just to put proper Fixes: tags
>>>>   on it. Eventually those commits are part of one out of two series, I put
>>>>   the respective kernel release version as a tag to the Cc: stable line.
>>>>
>>>> I couldn't reproduce the full lockdep splat on my setup, but at least
>>>> could show one instance and prove that these patches fixes that.
>>>>
>>>>
>>> For the series:
>>>
>>> Acked-by: Christoffer Dall <christoffer.dall@arm.com>
>>
>> Shall I put the patches on their route to Linus?
> If you're about to send something, yes please (saves me having to send
> you a pull request). In that case, please add my

Yes, I do - and I was keeping my eyes on this series anyway.

Thanks,

Paolo

> Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> 
> to the whole series.
> 
> Thanks,
> 
> 	M.
> 

WARNING: multiple messages have this Message-ID (diff)
From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] KVM: arm/arm64: Fix locking issues
Date: Tue, 15 May 2018 14:05:38 +0200	[thread overview]
Message-ID: <e33bdec4-97d9-fcc1-da1f-2c6d87b2c56d@redhat.com> (raw)
In-Reply-To: <b8aae9d6-1413-157d-52c2-e06511975e11@arm.com>

On 15/05/2018 13:54, Marc Zyngier wrote:
> On 15/05/18 12:35, Paolo Bonzini wrote:
>> On 15/05/2018 12:26, Christoffer Dall wrote:
>>> On Fri, May 11, 2018 at 03:20:11PM +0100, Andre Przywara wrote:
>>>> Jan recently reported lockdep complaints regarding various locks in our
>>>> VGIC emulation [1][2].
>>>> This boiled down to two separate issues:
>>>> - When promoting the vgic_irq->irq_lock to require IRQs being disabled,
>>>>   we forgot to amend some instances of this lock on the way. Also this
>>>>   needs to be applied to dependent locks as well. The first two patches
>>>>   fix that. The patch split is designed to simplify backporting.
>>>>   Those patches have been posted before, I am resending them as part
>>>>   of this series.
>>>> - Calling kvm_read_guest() requires us to be inside an SRCU critical
>>>>   section. On some architectures we are always in it when handling VCPU
>>>>   exits, but on ARM we need to lock it individually. Patches 3 and 4
>>>>   fix that, the split is again made to ease backporting.
>>>>   Each of the hunks fix an indiviual commit, but I refrained from
>>>>   splitting this down into eight patches just to put proper Fixes: tags
>>>>   on it. Eventually those commits are part of one out of two series, I put
>>>>   the respective kernel release version as a tag to the Cc: stable line.
>>>>
>>>> I couldn't reproduce the full lockdep splat on my setup, but at least
>>>> could show one instance and prove that these patches fixes that.
>>>>
>>>>
>>> For the series:
>>>
>>> Acked-by: Christoffer Dall <christoffer.dall@arm.com>
>>
>> Shall I put the patches on their route to Linus?
> If you're about to send something, yes please (saves me having to send
> you a pull request). In that case, please add my

Yes, I do - and I was keeping my eyes on this series anyway.

Thanks,

Paolo

> Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> 
> to the whole series.
> 
> Thanks,
> 
> 	M.
> 

  reply	other threads:[~2018-05-15 12:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 14:20 [PATCH 0/4] KVM: arm/arm64: Fix locking issues Andre Przywara
2018-05-11 14:20 ` Andre Przywara
2018-05-11 14:20 ` [PATCH 1/4] KVM: arm/arm64: Properly protect VGIC locks from IRQs Andre Przywara
2018-05-11 14:20   ` Andre Przywara
2018-05-11 14:20 ` [PATCH 2/4] KVM: arm/arm64: VGIC/ITS: Promote irq_lock() in update_affinity Andre Przywara
2018-05-11 14:20   ` Andre Przywara
2018-05-11 14:20 ` [PATCH 3/4] KVM: arm/arm64: VGIC/ITS: protect kvm_read_guest() calls with SRCU lock Andre Przywara
2018-05-11 14:20   ` Andre Przywara
2018-05-11 14:20 ` [PATCH 4/4] KVM: arm/arm64: VGIC/ITS save/restore: protect kvm_read_guest() calls Andre Przywara
2018-05-11 14:20   ` Andre Przywara
2018-05-15 10:26 ` [PATCH 0/4] KVM: arm/arm64: Fix locking issues Christoffer Dall
2018-05-15 10:26   ` Christoffer Dall
2018-05-15 11:35   ` Paolo Bonzini
2018-05-15 11:35     ` Paolo Bonzini
2018-05-15 11:54     ` Marc Zyngier
2018-05-15 11:54       ` Marc Zyngier
2018-05-15 12:05       ` Paolo Bonzini [this message]
2018-05-15 12:05         ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e33bdec4-97d9-fcc1-da1f-2c6d87b2c56d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=andre.przywara@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=eric.auger@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.