From: Jing Zhang <jingzhangos@google.com>
To: KVM <kvm@vger.kernel.org>, KVMARM <kvmarm@lists.linux.dev>,
ARMLinux <linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@google.com>,
Joey Gouly <joey.gouly@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Andre Przywara <andre.przywara@arm.com>,
Colton Lewis <coltonlewis@google.coma>,
Raghavendra Rao Ananta <rananta@google.com>,
Jing Zhang <jingzhangos@google.com>
Subject: [PATCH v1 2/4] KVM: arm64: vgic-its: Add a dummy DTE/ITE if necessary in ITS tables save operation
Date: Tue, 5 Nov 2024 11:34:20 -0800 [thread overview]
Message-ID: <20241105193422.1094875-3-jingzhangos@google.com> (raw)
In-Reply-To: <20241105193422.1094875-1-jingzhangos@google.com>
In device tables/ITTs, DTEs/ITEs are implemented as a static single
linked list. But the head of the list might not be the first DTE/ITE in
the table. That's why in the restore operation, the DTs/ITTs have to be
scanned to find the first valid DTE/ITE (head of the list).
Add a dummy DTE/ITE in the first entry of the table if the first entry
doesn't have a valid DTE/ITE. This dummy DTE/ITE points to the first
valid DTE/ITE if there is a valid one.
This change paves the way for future incoming changes which will utilize
the fixed head the DTE/ITE list to avoid scanning uncessary table
entries.
No functional change intended.
Signed-off-by: Jing Zhang <jingzhangos@google.com>
---
arch/arm64/kvm/vgic/vgic-its.c | 56 ++++++++++++++++++++++++++++++++--
arch/arm64/kvm/vgic/vgic.h | 6 ++++
2 files changed, 59 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kvm/vgic/vgic-its.c b/arch/arm64/kvm/vgic/vgic-its.c
index ba945ba78cc7..953af024d94a 100644
--- a/arch/arm64/kvm/vgic/vgic-its.c
+++ b/arch/arm64/kvm/vgic/vgic-its.c
@@ -2176,10 +2176,12 @@ static int vgic_its_ite_cmp(void *priv, const struct list_head *a,
static int vgic_its_save_itt(struct vgic_its *its, struct its_device *device)
{
const struct vgic_its_abi *abi = vgic_its_get_abi(its);
+ struct its_ite *ite, *first_ite = NULL;
+ struct kvm *kvm = its->dev->kvm;
gpa_t base = device->itt_addr;
- struct its_ite *ite;
- int ret;
int ite_esz = abi->ite_esz;
+ u64 val = 0;
+ int ret;
list_sort(NULL, &device->itt_head, vgic_its_ite_cmp);
@@ -2198,7 +2200,24 @@ static int vgic_its_save_itt(struct vgic_its *its, struct its_device *device)
ret = vgic_its_save_ite(its, device, ite, gpa, ite_esz);
if (ret)
return ret;
+
+ if (!first_ite)
+ first_ite = ite;
}
+
+ /*
+ * As for DTEs, add a dummy ITE if necessary for ITT to avoid uncessary
+ * sanning in the store operation.
+ */
+ if (first_ite && first_ite->event_id)
+ val = (u64)first_ite->event_id << KVM_ITS_ITE_NEXT_SHIFT;
+
+ if (!first_ite || first_ite->event_id) {
+ val |= KVM_ITS_ENTRY_DUMMY_MAGIC << KVM_ITS_ENTRY_DUMMY_SHIFT;
+ val = cpu_to_le64(val);
+ vgic_write_guest_lock(kvm, base, &val, ite_esz);
+ }
+
return 0;
}
@@ -2328,8 +2347,11 @@ static int vgic_its_save_device_tables(struct vgic_its *its)
{
const struct vgic_its_abi *abi = vgic_its_get_abi(its);
u64 baser = its->baser_device_table;
- struct its_device *dev;
+ struct its_device *dev, *first_dev = NULL;
+ struct kvm *kvm = its->dev->kvm;
int dte_esz = abi->dte_esz;
+ gpa_t dummy_eaddr;
+ u64 val = 0;
if (!(baser & GITS_BASER_VALID))
return 0;
@@ -2351,7 +2373,35 @@ static int vgic_its_save_device_tables(struct vgic_its *its)
ret = vgic_its_save_dte(its, dev, eaddr, dte_esz);
if (ret)
return ret;
+
+ if (!first_dev)
+ first_dev = dev;
}
+
+ /*
+ * The valid DTEs in the device table are linked with a static single
+ * linked list, but the list head is not always the first DTE. That's
+ * why the restore operation has to scan the device table from the first
+ * entry all the time.
+ * To avoid the uncessary scanning in the restore operation, if the
+ * first valid DTE is not the first one in the table, add a dummy DTE
+ * with valid bit as 0 pointing to the first valid DTE.
+ * This way, the first DTE in the table is always the head of the DTE
+ * list. It is either a valid DTE or a dummy DTE (V= 0) pointing to the
+ * first valid DTE if there is a valid DTE in the table.
+ */
+ if (first_dev && first_dev->device_id)
+ val = (u64)first_dev->device_id << KVM_ITS_DTE_DUMMY_NEXT_SHIFT;
+
+ if (!first_dev || first_dev->device_id) {
+ if (!vgic_its_check_id(its, baser, 0, &dummy_eaddr))
+ return -EINVAL;
+
+ val |= KVM_ITS_ENTRY_DUMMY_MAGIC << KVM_ITS_ENTRY_DUMMY_SHIFT;
+ val = cpu_to_le64(val);
+ vgic_write_guest_lock(kvm, dummy_eaddr, &val, dte_esz);
+ }
+
return 0;
}
diff --git a/arch/arm64/kvm/vgic/vgic.h b/arch/arm64/kvm/vgic/vgic.h
index f2486b4d9f95..93314f249343 100644
--- a/arch/arm64/kvm/vgic/vgic.h
+++ b/arch/arm64/kvm/vgic/vgic.h
@@ -86,6 +86,12 @@
#define KVM_ITS_L1E_VALID_MASK BIT_ULL(63)
/* we only support 64 kB translation table page size */
#define KVM_ITS_L1E_ADDR_MASK GENMASK_ULL(51, 16)
+/* Macros for dummy ITE/DTE */
+#define KVM_ITS_ENTRY_DUMMY_SHIFT 0
+#define KVM_ITS_ENTRY_DUMMY_MASK GENMASK_ULL(15, 0)
+#define KVM_ITS_ENTRY_DUMMY_MAGIC 0xdafe
+#define KVM_ITS_DTE_DUMMY_NEXT_SHIFT 16
+#define KVM_ITS_DTE_DUMMY_NEXT_MASK GENMASK(48, 16)
#define KVM_VGIC_V3_RDIST_INDEX_MASK GENMASK_ULL(11, 0)
#define KVM_VGIC_V3_RDIST_FLAGS_MASK GENMASK_ULL(15, 12)
--
2.47.0.199.ga7371fff76-goog
next prev parent reply other threads:[~2024-11-05 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 19:34 [PATCH v1 0/4] Fix a bug in VGIC ITS tables' save/restore Jing Zhang
2024-11-05 19:34 ` [PATCH v1 1/4] KVM: selftests: aarch64: Test VGIC ITS tables save/restore Jing Zhang
2024-11-05 19:34 ` Jing Zhang [this message]
2024-11-05 19:34 ` [PATCH v1 3/4] KVM: arm64: vgic-its: Return device/event id instead of offset in ITS tables restore Jing Zhang
2024-11-05 19:34 ` [PATCH v1 4/4] KVM: arm64: vgic-its: Utilize the dummy entry in ITS tables restoring Jing Zhang
2024-11-05 21:33 ` [PATCH v1 0/4] Fix a bug in VGIC ITS tables' save/restore Oliver Upton
2024-11-05 21:56 ` Jing Zhang
2024-11-05 21:58 ` Oliver Upton
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=20241105193422.1094875-3-jingzhangos@google.com \
--to=jingzhangos@google.com \
--cc=andre.przywara@arm.com \
--cc=coltonlewis@google.coma \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=rananta@google.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox