From: Ryan Roberts <ryan.roberts@arm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/2] KVM fixes for exotic configurations
Date: Thu, 3 Nov 2022 15:05:05 +0000 [thread overview]
Message-ID: <20221103150507.32948-1-ryan.roberts@arm.com> (raw)
I've been adding support for FEAT_LPA2 to KVM and as part of that work have been
testing various (84) configurations of HW, host and guest kernels on FVP. This
has thrown up a couple of pre-existing bugs, for which the fixes are provided.
Thanks,
Ryan
Ryan Roberts (2):
KVM: arm64: Fix kvm init failure when mode!=vhe and VA_BITS=52.
KVM: arm64: Fix PAR_TO_HPFAR() to work independently of PA_BITS.
arch/arm64/include/asm/kvm_arm.h | 6 +++++-
arch/arm64/kvm/arm.c | 20 +++-----------------
arch/arm64/kvm/mmu.c | 28 +++++++++++++++++++++++++++-
3 files changed, 35 insertions(+), 19 deletions(-)
--
2.17.1
_______________________________________________
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: Ryan Roberts <ryan.roberts@arm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvmarm@lists.cs.columbia.edu
Subject: [PATCH v1 0/2] KVM fixes for exotic configurations
Date: Thu, 3 Nov 2022 15:05:05 +0000 [thread overview]
Message-ID: <20221103150507.32948-1-ryan.roberts@arm.com> (raw)
Message-ID: <20221103150505.5CutDokw9-MMMkaI-CQ_RPH06FHKtvtChzE1qDqmWmw@z> (raw)
I've been adding support for FEAT_LPA2 to KVM and as part of that work have been
testing various (84) configurations of HW, host and guest kernels on FVP. This
has thrown up a couple of pre-existing bugs, for which the fixes are provided.
Thanks,
Ryan
Ryan Roberts (2):
KVM: arm64: Fix kvm init failure when mode!=vhe and VA_BITS=52.
KVM: arm64: Fix PAR_TO_HPFAR() to work independently of PA_BITS.
arch/arm64/include/asm/kvm_arm.h | 6 +++++-
arch/arm64/kvm/arm.c | 20 +++-----------------
arch/arm64/kvm/mmu.c | 28 +++++++++++++++++++++++++++-
3 files changed, 35 insertions(+), 19 deletions(-)
--
2.17.1
next reply other threads:[~2022-11-03 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:05 Ryan Roberts [this message]
2022-11-03 15:05 ` [PATCH v1 0/2] KVM fixes for exotic configurations Ryan Roberts
2022-11-03 15:05 ` [PATCH v1 1/2] KVM: arm64: Fix kvm init failure when mode!=vhe and VA_BITS=52 Ryan Roberts
2022-11-03 15:05 ` Ryan Roberts
2022-11-03 15:05 ` [PATCH v1 2/2] KVM: arm64: Fix PAR_TO_HPFAR() to work independently of PA_BITS Ryan Roberts
2022-11-03 15:05 ` Ryan Roberts
2022-11-10 19:25 ` [PATCH v1 0/2] KVM fixes for exotic configurations Marc Zyngier
2022-11-10 19:25 ` 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=20221103150507.32948-1-ryan.roberts@arm.com \
--to=ryan.roberts@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox