From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Cc: James Morse <james.morse@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
kernel-team@android.com,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Ricardo Koller <ricarkol@google.com>,
Eric Auger <eric.auger@redhat.com>,
stable@vger.kernel.org,
Alexandru Elisei <alexandru.elisei@arm.com>,
Oliver Upton <oupton@google.com>
Subject: Re: [PATCH v2] KVM: arm64: vgic: Resample HW pending state on deactivation
Date: Fri, 20 Aug 2021 08:58:22 +0100 [thread overview]
Message-ID: <162944629227.1671663.6947098620852443792.b4-ty@kernel.org> (raw)
In-Reply-To: <20210819180305.1670525-1-maz@kernel.org>
On Thu, 19 Aug 2021 19:03:05 +0100, Marc Zyngier wrote:
> When a mapped level interrupt (a timer, for example) is deactivated
> by the guest, the corresponding host interrupt is equally deactivated.
> However, the fate of the pending state still needs to be dealt
> with in SW.
>
> This is specially true when the interrupt was in the active+pending
> state in the virtual distributor at the point where the guest
> was entered. On exit, the pending state is potentially stale
> (the guest may have put the interrupt in a non-pending state).
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: vgic: Resample HW pending state on deactivation
commit: 3134cc8beb69d0db9de651081707c4651c011621
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
stable@vger.kernel.org,
Raghavendra Rao Ananta <rananta@google.com>,
kernel-team@android.com
Subject: Re: [PATCH v2] KVM: arm64: vgic: Resample HW pending state on deactivation
Date: Fri, 20 Aug 2021 08:58:22 +0100 [thread overview]
Message-ID: <162944629227.1671663.6947098620852443792.b4-ty@kernel.org> (raw)
In-Reply-To: <20210819180305.1670525-1-maz@kernel.org>
On Thu, 19 Aug 2021 19:03:05 +0100, Marc Zyngier wrote:
> When a mapped level interrupt (a timer, for example) is deactivated
> by the guest, the corresponding host interrupt is equally deactivated.
> However, the fate of the pending state still needs to be dealt
> with in SW.
>
> This is specially true when the interrupt was in the active+pending
> state in the virtual distributor at the point where the guest
> was entered. On exit, the pending state is potentially stale
> (the guest may have put the interrupt in a non-pending state).
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: vgic: Resample HW pending state on deactivation
commit: 3134cc8beb69d0db9de651081707c4651c011621
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Cc: James Morse <james.morse@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
kernel-team@android.com,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Ricardo Koller <ricarkol@google.com>,
Eric Auger <eric.auger@redhat.com>,
stable@vger.kernel.org,
Alexandru Elisei <alexandru.elisei@arm.com>,
Oliver Upton <oupton@google.com>
Subject: Re: [PATCH v2] KVM: arm64: vgic: Resample HW pending state on deactivation
Date: Fri, 20 Aug 2021 08:58:22 +0100 [thread overview]
Message-ID: <162944629227.1671663.6947098620852443792.b4-ty@kernel.org> (raw)
In-Reply-To: <20210819180305.1670525-1-maz@kernel.org>
On Thu, 19 Aug 2021 19:03:05 +0100, Marc Zyngier wrote:
> When a mapped level interrupt (a timer, for example) is deactivated
> by the guest, the corresponding host interrupt is equally deactivated.
> However, the fate of the pending state still needs to be dealt
> with in SW.
>
> This is specially true when the interrupt was in the active+pending
> state in the virtual distributor at the point where the guest
> was entered. On exit, the pending state is potentially stale
> (the guest may have put the interrupt in a non-pending state).
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: vgic: Resample HW pending state on deactivation
commit: 3134cc8beb69d0db9de651081707c4651c011621
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-20 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 18:03 [PATCH v2] KVM: arm64: vgic: Resample HW pending state on deactivation Marc Zyngier
2021-08-19 18:03 ` Marc Zyngier
2021-08-19 18:03 ` Marc Zyngier
2021-08-20 7:58 ` Marc Zyngier [this message]
2021-08-20 7:58 ` Marc Zyngier
2021-08-20 7:58 ` Marc Zyngier
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=162944629227.1671663.6947098620852443792.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@google.com \
--cc=rananta@google.com \
--cc=ricarkol@google.com \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@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.