From: Will Deacon <will@kernel.org> To: kvmarm@lists.linux.dev Cc: linux-arm-kernel@lists.infradead.org, Will Deacon <will@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Gavin Shan <gshan@redhat.com>, Marc Zyngier <maz@kernel.org>, Mostafa Saleh <smostafa@google.com>, Oliver Upton <oliver.upton@linux.dev>, Quentin Perret <qperret@google.com>, Raghavendra Rao Ananta <rananta@google.com>, Ryan Roberts <ryan.roberts@arm.com>, Shaoqin Huang <shahuang@redhat.com>, Suzuki K Poulose <suzuki.poulose@arm.com>, Zenghui Yu <yuzenghui@huawei.com> Subject: [PATCH 0/3] KVM: arm64: TLBI fixes for the pgtable code Date: Mon, 25 Mar 2024 18:51:55 +0000 [thread overview] Message-ID: <20240325185158.8565-1-will@kernel.org> (raw) Hi folks, While debugging something else, I noticed a few TLBI oddities in KVM's page-table code. These were found by inspection, so please have a good look as I may be mistaken. Patches against -rc1. Cheers, Will Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Gavin Shan <gshan@redhat.com> Cc: Marc Zyngier <maz@kernel.org> Cc: Mostafa Saleh <smostafa@google.com> Cc: Oliver Upton <oliver.upton@linux.dev> Cc: Quentin Perret <qperret@google.com> Cc: Raghavendra Rao Ananta <rananta@google.com> Cc: Ryan Roberts <ryan.roberts@arm.com> Cc: Shaoqin Huang <shahuang@redhat.com> Cc: Suzuki K Poulose <suzuki.poulose@arm.com> Cc: Zenghui Yu <yuzenghui@huawei.com> --->8 Will Deacon (3): KVM: arm64: Don't defer TLB invalidation when zapping table entries KVM: arm64: Don't pass a TLBI level hint when zapping table entries KVM: arm64: Use TLBI_TTL_UNKNOWN in __kvm_tlb_flush_vmid_range() arch/arm64/kvm/hyp/nvhe/tlb.c | 3 ++- arch/arm64/kvm/hyp/pgtable.c | 12 ++++++++---- arch/arm64/kvm/hyp/vhe/tlb.c | 3 ++- 3 files changed, 12 insertions(+), 6 deletions(-) -- 2.44.0.396.g6e790dbe36-goog
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org> To: kvmarm@lists.linux.dev Cc: linux-arm-kernel@lists.infradead.org, Will Deacon <will@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Gavin Shan <gshan@redhat.com>, Marc Zyngier <maz@kernel.org>, Mostafa Saleh <smostafa@google.com>, Oliver Upton <oliver.upton@linux.dev>, Quentin Perret <qperret@google.com>, Raghavendra Rao Ananta <rananta@google.com>, Ryan Roberts <ryan.roberts@arm.com>, Shaoqin Huang <shahuang@redhat.com>, Suzuki K Poulose <suzuki.poulose@arm.com>, Zenghui Yu <yuzenghui@huawei.com> Subject: [PATCH 0/3] KVM: arm64: TLBI fixes for the pgtable code Date: Mon, 25 Mar 2024 18:51:55 +0000 [thread overview] Message-ID: <20240325185158.8565-1-will@kernel.org> (raw) Hi folks, While debugging something else, I noticed a few TLBI oddities in KVM's page-table code. These were found by inspection, so please have a good look as I may be mistaken. Patches against -rc1. Cheers, Will Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Gavin Shan <gshan@redhat.com> Cc: Marc Zyngier <maz@kernel.org> Cc: Mostafa Saleh <smostafa@google.com> Cc: Oliver Upton <oliver.upton@linux.dev> Cc: Quentin Perret <qperret@google.com> Cc: Raghavendra Rao Ananta <rananta@google.com> Cc: Ryan Roberts <ryan.roberts@arm.com> Cc: Shaoqin Huang <shahuang@redhat.com> Cc: Suzuki K Poulose <suzuki.poulose@arm.com> Cc: Zenghui Yu <yuzenghui@huawei.com> --->8 Will Deacon (3): KVM: arm64: Don't defer TLB invalidation when zapping table entries KVM: arm64: Don't pass a TLBI level hint when zapping table entries KVM: arm64: Use TLBI_TTL_UNKNOWN in __kvm_tlb_flush_vmid_range() arch/arm64/kvm/hyp/nvhe/tlb.c | 3 ++- arch/arm64/kvm/hyp/pgtable.c | 12 ++++++++---- arch/arm64/kvm/hyp/vhe/tlb.c | 3 ++- 3 files changed, 12 insertions(+), 6 deletions(-) -- 2.44.0.396.g6e790dbe36-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-03-25 18:52 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 18:51 Will Deacon [this message] 2024-03-25 18:51 ` [PATCH 0/3] KVM: arm64: TLBI fixes for the pgtable code Will Deacon 2024-03-25 18:51 ` [PATCH 1/3] KVM: arm64: Don't defer TLB invalidation when zapping table entries Will Deacon 2024-03-25 18:51 ` Will Deacon 2024-03-26 8:34 ` Oliver Upton 2024-03-26 8:34 ` Oliver Upton 2024-03-26 14:31 ` Oliver Upton 2024-03-26 14:31 ` Oliver Upton 2024-03-26 16:10 ` Will Deacon 2024-03-26 16:10 ` Will Deacon 2024-03-26 16:14 ` Oliver Upton 2024-03-26 16:14 ` Oliver Upton 2024-03-25 18:51 ` [PATCH 2/3] KVM: arm64: Don't pass a TLBI level hint " Will Deacon 2024-03-25 18:51 ` Will Deacon 2024-03-26 8:37 ` Oliver Upton 2024-03-26 8:37 ` Oliver Upton 2024-03-26 9:34 ` Will Deacon 2024-03-26 9:34 ` Will Deacon 2024-03-26 13:12 ` Oliver Upton 2024-03-26 13:12 ` Oliver Upton 2024-03-25 18:51 ` [PATCH 3/3] KVM: arm64: Use TLBI_TTL_UNKNOWN in __kvm_tlb_flush_vmid_range() Will Deacon 2024-03-25 18:51 ` Will Deacon 2024-03-26 13:48 ` Ryan Roberts 2024-03-26 13:48 ` Ryan Roberts 2024-03-27 12:45 ` Will Deacon 2024-03-27 12:45 ` Will Deacon
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=20240325185158.8565-1-will@kernel.org \ --to=will@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=gshan@redhat.com \ --cc=kvmarm@lists.linux.dev \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=maz@kernel.org \ --cc=oliver.upton@linux.dev \ --cc=qperret@google.com \ --cc=rananta@google.com \ --cc=ryan.roberts@arm.com \ --cc=shahuang@redhat.com \ --cc=smostafa@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: linkBe 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.