All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
To: maz@kernel.org
Cc: catalin.marinas@arm.com, will@kernel.org, andre.przywara@arm.com,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	darren@os.amperecomputing.com,
	d.scott.phillips@amperecomputing.com,
	gankulkarni@os.amperecomputing.com
Subject: [PATCH 0/2] KVM: arm64: nv: Fix issue with Stage 2 MMU init for Nested case.
Date: Mon, 22 Nov 2021 01:58:01 -0800	[thread overview]
Message-ID: <20211122095803.28943-1-gankulkarni@os.amperecomputing.com> (raw)

The Guest Hypervisor stage 2 mmu table was used while creating map
and subsequent tlb flush for Nested VM. This resulted in unresolvable
stage 2 fault for Nested VM since tlb was invalidated with
Guest-Hypervisor VMID.

Patch 1/2 should be applied before the NV patchset[1].
Patch 2/2 can be squashed in to Commit 1776c91346b6 ("KVM: arm64: nv:
Support multiple nested Stage-2 mmu structures")[2].

[1] https://lore.kernel.org/kvmarm/20210510165920.1913477-1-maz@kernel.org/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/
branch kvm-arm64/nv-5.13

Ganapatrao Kulkarni (2):
  KVM: arm64: Use appropriate mmu pointer in stage2 page table init.
  KVM: arm64: nv: fixup! Support multiple nested Stage-2 mmu structures

 arch/arm64/include/asm/kvm_pgtable.h  | 6 ++++--
 arch/arm64/kvm/hyp/nvhe/mem_protect.c | 2 +-
 arch/arm64/kvm/hyp/pgtable.c          | 3 ++-
 arch/arm64/kvm/mmu.c                  | 2 +-
 arch/arm64/kvm/nested.c               | 9 +++++++++
 5 files changed, 17 insertions(+), 5 deletions(-)

-- 
2.27.0


WARNING: multiple messages have this Message-ID (diff)
From: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
To: maz@kernel.org
Cc: d.scott.phillips@amperecomputing.com, kvm@vger.kernel.org,
	catalin.marinas@arm.com, darren@os.amperecomputing.com,
	andre.przywara@arm.com, gankulkarni@os.amperecomputing.com,
	will@kernel.org, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] KVM: arm64: nv: Fix issue with Stage 2 MMU init for Nested case.
Date: Mon, 22 Nov 2021 01:58:01 -0800	[thread overview]
Message-ID: <20211122095803.28943-1-gankulkarni@os.amperecomputing.com> (raw)

The Guest Hypervisor stage 2 mmu table was used while creating map
and subsequent tlb flush for Nested VM. This resulted in unresolvable
stage 2 fault for Nested VM since tlb was invalidated with
Guest-Hypervisor VMID.

Patch 1/2 should be applied before the NV patchset[1].
Patch 2/2 can be squashed in to Commit 1776c91346b6 ("KVM: arm64: nv:
Support multiple nested Stage-2 mmu structures")[2].

[1] https://lore.kernel.org/kvmarm/20210510165920.1913477-1-maz@kernel.org/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/
branch kvm-arm64/nv-5.13

Ganapatrao Kulkarni (2):
  KVM: arm64: Use appropriate mmu pointer in stage2 page table init.
  KVM: arm64: nv: fixup! Support multiple nested Stage-2 mmu structures

 arch/arm64/include/asm/kvm_pgtable.h  | 6 ++++--
 arch/arm64/kvm/hyp/nvhe/mem_protect.c | 2 +-
 arch/arm64/kvm/hyp/pgtable.c          | 3 ++-
 arch/arm64/kvm/mmu.c                  | 2 +-
 arch/arm64/kvm/nested.c               | 9 +++++++++
 5 files changed, 17 insertions(+), 5 deletions(-)

-- 
2.27.0

_______________________________________________
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: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
To: maz@kernel.org
Cc: catalin.marinas@arm.com, will@kernel.org, andre.przywara@arm.com,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	darren@os.amperecomputing.com,
	d.scott.phillips@amperecomputing.com,
	gankulkarni@os.amperecomputing.com
Subject: [PATCH 0/2] KVM: arm64: nv: Fix issue with Stage 2 MMU init for Nested case.
Date: Mon, 22 Nov 2021 01:58:01 -0800	[thread overview]
Message-ID: <20211122095803.28943-1-gankulkarni@os.amperecomputing.com> (raw)

The Guest Hypervisor stage 2 mmu table was used while creating map
and subsequent tlb flush for Nested VM. This resulted in unresolvable
stage 2 fault for Nested VM since tlb was invalidated with
Guest-Hypervisor VMID.

Patch 1/2 should be applied before the NV patchset[1].
Patch 2/2 can be squashed in to Commit 1776c91346b6 ("KVM: arm64: nv:
Support multiple nested Stage-2 mmu structures")[2].

[1] https://lore.kernel.org/kvmarm/20210510165920.1913477-1-maz@kernel.org/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/
branch kvm-arm64/nv-5.13

Ganapatrao Kulkarni (2):
  KVM: arm64: Use appropriate mmu pointer in stage2 page table init.
  KVM: arm64: nv: fixup! Support multiple nested Stage-2 mmu structures

 arch/arm64/include/asm/kvm_pgtable.h  | 6 ++++--
 arch/arm64/kvm/hyp/nvhe/mem_protect.c | 2 +-
 arch/arm64/kvm/hyp/pgtable.c          | 3 ++-
 arch/arm64/kvm/mmu.c                  | 2 +-
 arch/arm64/kvm/nested.c               | 9 +++++++++
 5 files changed, 17 insertions(+), 5 deletions(-)

-- 
2.27.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-11-22  9:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  9:58 Ganapatrao Kulkarni [this message]
2021-11-22  9:58 ` [PATCH 0/2] KVM: arm64: nv: Fix issue with Stage 2 MMU init for Nested case Ganapatrao Kulkarni
2021-11-22  9:58 ` Ganapatrao Kulkarni
2021-11-22  9:58 ` [PATCH 1/2] KVM: arm64: Use appropriate mmu pointer in stage2 page table init Ganapatrao Kulkarni
2021-11-22  9:58   ` Ganapatrao Kulkarni
2021-11-22  9:58   ` Ganapatrao Kulkarni
2021-11-25 13:49   ` Marc Zyngier
2021-11-25 13:49     ` Marc Zyngier
2021-11-25 13:49     ` Marc Zyngier
2021-11-26  5:45     ` Ganapatrao Kulkarni
2021-11-26  5:45       ` Ganapatrao Kulkarni
2021-11-26  5:45       ` Ganapatrao Kulkarni
2021-11-26 10:50       ` Marc Zyngier
2021-11-26 10:50         ` Marc Zyngier
2021-11-26 10:50         ` Marc Zyngier
2021-11-26 16:51         ` Ganapatrao Kulkarni
2021-11-26 16:51           ` Ganapatrao Kulkarni
2021-11-26 16:51           ` Ganapatrao Kulkarni
2021-11-22  9:58 ` [PATCH 2/2] KVM: arm64: nv: fixup! Support multiple nested Stage-2 mmu structures Ganapatrao Kulkarni
2021-11-22  9:58   ` Ganapatrao Kulkarni
2021-11-22  9:58   ` Ganapatrao Kulkarni
2021-11-25 14:23   ` Marc Zyngier
2021-11-25 14:23     ` Marc Zyngier
2021-11-25 14:23     ` Marc Zyngier
2021-11-26  5:59     ` Ganapatrao Kulkarni
2021-11-26  5:59       ` Ganapatrao Kulkarni
2021-11-26  5:59       ` Ganapatrao Kulkarni
2021-11-26 15:28       ` Marc Zyngier
2021-11-26 16:33       ` Marc Zyngier
2021-11-26 19:20       ` Marc Zyngier
2021-11-26 19:20         ` Marc Zyngier
2021-11-26 19:20         ` Marc Zyngier
2021-11-29  6:00         ` Ganapatrao Kulkarni
2021-11-29  6:00           ` Ganapatrao Kulkarni
2021-11-29  6:00           ` Ganapatrao Kulkarni

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=20211122095803.28943-1-gankulkarni@os.amperecomputing.com \
    --to=gankulkarni@os.amperecomputing.com \
    --cc=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=d.scott.phillips@amperecomputing.com \
    --cc=darren@os.amperecomputing.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=will@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.