[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230119234405.349644-1-gshan@redhat.com>
Date: Fri, 20 Jan 2023 07:44:02 +0800
From: Gavin Shan <gshan@...hat.com>
To: kvmarm@...ts.linux.dev
Cc: kvmarm@...ts.cs.columbia.edu, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
pbonzini@...hat.com, corbet@....net, maz@...nel.org,
oliver.upton@...ux.dev, will@...nel.org, gshan@...hat.com,
ricarkol@...gle.com, eric.auger@...hat.com, yuzhe@...china.com,
renzhengeek@...il.com, reijiw@...gle.com, ardb@...nel.org,
Julia.Lawall@...ia.fr, yuzenghui@...wei.com, seanjc@...gle.com,
shan.gavin@...il.com
Subject: [PATCH v2 0/3] Improve dirty ring warning report
It has been known case where no running VCPU context exists when the
vgic/its tables are saved. There are other two unknown cases where we
don't have the running VCPU context: (a) restore vgic3 LPI pending
status. (b) restoring vgic3 pending tables.
PATCH[1] adds unified helper vgic_write_guest_lock()
PATCH[2 - 3] allows no-running-vcpu context for (a) and (b)
v1: https://lore.kernel.org/kvmarm/20230116040405.260935-1-gshan@redhat.com/T/#t
Changelog
=========
v2:
* Add unified helper vgic_write_guest_lock() (Oliver)
* Dropped two patches to refactor mark_page_dirty_in_slot() (Sean)
Gavin Shan (3):
KVM: arm64: Add helper vgic_write_guest_lock()
KVM: arm64: Allow no running vcpu on restoring vgic3 LPI pending
status
KVM: arm64: Allow no running vcpu on saving vgic3 pending table
Documentation/virt/kvm/api.rst | 10 +++++++---
arch/arm64/kvm/vgic-sys-reg-v3.c | 1 +
arch/arm64/kvm/vgic/vgic-irqfd.c | 1 +
arch/arm64/kvm/vgic/vgic-its.c | 13 +++++--------
arch/arm64/kvm/vgic/vgic-mmio-v2.c | 1 +
arch/arm64/kvm/vgic/vgic-mmio.c | 1 +
arch/arm64/kvm/vgic/vgic-v3.c | 4 ++--
arch/arm64/kvm/vgic/vgic-v4.c | 1 +
arch/arm64/kvm/vgic/vgic.c | 1 +
arch/arm64/kvm/vgic/vgic.h | 13 +++++++++++++
include/kvm/arm_vgic.h | 2 +-
11 files changed, 34 insertions(+), 14 deletions(-)
--
2.23.0
Powered by blists - more mailing lists