From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Julien Thierry <julien.thierry@arm.com>,
linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Cc: Marc Zyngier <marc.zyngier@arm.com>, stable@vger.kernel.org
Subject: Re: [PATCH 1/4] KVM: arm/arm64: vgic: Do not cond_resched_lock() with IRQs disabled
Date: Tue, 20 Nov 2018 13:25:31 +0000 [thread overview]
Message-ID: <20181120132532.962F420851@mail.kernel.org> (raw)
In-Reply-To: <1542647279-46609-2-git-send-email-julien.thierry@arm.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.19.2, v4.18.19, v4.14.81, v4.9.137, v4.4.163, v3.18.125.
v4.19.2: Build OK!
v4.18.19: Build OK!
v4.14.81: Failed to apply! Possible dependencies:
Unable to calculate
v4.9.137: Failed to apply! Possible dependencies:
Unable to calculate
v4.4.163: Failed to apply! Possible dependencies:
370a0ec18199 ("KVM: arm/arm64: Let vcpu thread modify its own active state")
v3.18.125: Failed to apply! Possible dependencies:
370a0ec18199 ("KVM: arm/arm64: Let vcpu thread modify its own active state")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-20 13:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 17:07 [PATCH 0/4] KVM: arm/arm64: vgic: Use raw_spinlock for locks taken in IRQ context Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-19 17:07 ` [PATCH 1/4] KVM: arm/arm64: vgic: Do not cond_resched_lock() with IRQs disabled Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-20 13:25 ` Sasha Levin [this message]
2018-11-20 14:18 ` Christoffer Dall
2018-11-20 14:18 ` Christoffer Dall
2018-11-20 14:37 ` Marc Zyngier
2018-11-20 14:37 ` Marc Zyngier
2018-11-20 17:22 ` Julien Thierry
2018-11-20 17:22 ` Julien Thierry
2018-11-19 17:07 ` [PATCH 2/4] KVM: arm/arm64: vgic: Make vgic_irq->irq_lock a raw_spinlock Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-19 17:07 ` [PATCH 3/4] KVM: arm/arm64: vgic: Make vgic_dist->lpi_list_lock " Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-19 17:07 ` [PATCH 4/4] KVM: arm/arm64: vgic: Make vgic_cpu->ap_list_lock " Julien Thierry
2018-11-19 17:07 ` Julien Thierry
2018-11-20 14:20 ` [PATCH 0/4] KVM: arm/arm64: vgic: Use raw_spinlock for locks taken in IRQ context Christoffer Dall
2018-11-20 14:20 ` Christoffer Dall
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=20181120132532.962F420851@mail.kernel.org \
--to=sashal@kernel.org \
--cc=julien.thierry@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=stable@vger.kernel.org \
/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.