From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Cc: James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>, Andrew Jones <drjones@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
kernel-team@android.com
Subject: [PATCH v3 0/2] KVM: arm64: Assorted IPA size fixes
Date: Thu, 11 Mar 2021 10:00:14 +0000 [thread overview]
Message-ID: <20210311100016.3830038-1-maz@kernel.org> (raw)
This is a rework of an initial patch posted a couple of days back[1]
While working on enabling KVM on "reduced IPA size" systems, I realise
we have a couple of issues, some of while do impact userspace.
The first issue is that we accept the creation of a "default IPA size"
VM (40 bits) even when the HW doesn't support it. Not good.
The second one is that we disallow a memslot to end right where the
IPA limit is. One page less and you're good, but that's not quite what
it should be.
I intend for both patches to be backported to -stable.
Thanks,
M.
* From v2 [2]:
- Fix silly printk blunder
- Added Cc-stable and Fixes tags
* From v1 [1]:
- Don't try to cap the default IPA size. If userspace uses 0 with an
expectation that it will get 40bits, we should abide by it and
return an error immediately (noticed by Andrew)
- Added a new patch to fix the exclusive nature of the IPA limit
[1] https://lore.kernel.org/r/20210308174643.761100-1-maz@kernel.org
[2] https://lore.kernel.org/r/20210310104208.3819061-1-maz@kernel.org
Marc Zyngier (2):
KVM: arm64: Reject VM creation when the default IPA size is
unsupported
KVM: arm64: Fix exclusive limit for IPA size
Documentation/virt/kvm/api.rst | 3 +++
arch/arm64/kvm/mmu.c | 3 +--
arch/arm64/kvm/reset.c | 12 ++++++++----
3 files changed, 12 insertions(+), 6 deletions(-)
--
2.29.2
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: [PATCH v3 0/2] KVM: arm64: Assorted IPA size fixes
Date: Thu, 11 Mar 2021 10:00:14 +0000 [thread overview]
Message-ID: <20210311100016.3830038-1-maz@kernel.org> (raw)
This is a rework of an initial patch posted a couple of days back[1]
While working on enabling KVM on "reduced IPA size" systems, I realise
we have a couple of issues, some of while do impact userspace.
The first issue is that we accept the creation of a "default IPA size"
VM (40 bits) even when the HW doesn't support it. Not good.
The second one is that we disallow a memslot to end right where the
IPA limit is. One page less and you're good, but that's not quite what
it should be.
I intend for both patches to be backported to -stable.
Thanks,
M.
* From v2 [2]:
- Fix silly printk blunder
- Added Cc-stable and Fixes tags
* From v1 [1]:
- Don't try to cap the default IPA size. If userspace uses 0 with an
expectation that it will get 40bits, we should abide by it and
return an error immediately (noticed by Andrew)
- Added a new patch to fix the exclusive nature of the IPA limit
[1] https://lore.kernel.org/r/20210308174643.761100-1-maz@kernel.org
[2] https://lore.kernel.org/r/20210310104208.3819061-1-maz@kernel.org
Marc Zyngier (2):
KVM: arm64: Reject VM creation when the default IPA size is
unsupported
KVM: arm64: Fix exclusive limit for IPA size
Documentation/virt/kvm/api.rst | 3 +++
arch/arm64/kvm/mmu.c | 3 +--
arch/arm64/kvm/reset.c | 12 ++++++++----
3 files changed, 12 insertions(+), 6 deletions(-)
--
2.29.2
_______________________________________________
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: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Cc: James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>, Andrew Jones <drjones@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
kernel-team@android.com
Subject: [PATCH v3 0/2] KVM: arm64: Assorted IPA size fixes
Date: Thu, 11 Mar 2021 10:00:14 +0000 [thread overview]
Message-ID: <20210311100016.3830038-1-maz@kernel.org> (raw)
This is a rework of an initial patch posted a couple of days back[1]
While working on enabling KVM on "reduced IPA size" systems, I realise
we have a couple of issues, some of while do impact userspace.
The first issue is that we accept the creation of a "default IPA size"
VM (40 bits) even when the HW doesn't support it. Not good.
The second one is that we disallow a memslot to end right where the
IPA limit is. One page less and you're good, but that's not quite what
it should be.
I intend for both patches to be backported to -stable.
Thanks,
M.
* From v2 [2]:
- Fix silly printk blunder
- Added Cc-stable and Fixes tags
* From v1 [1]:
- Don't try to cap the default IPA size. If userspace uses 0 with an
expectation that it will get 40bits, we should abide by it and
return an error immediately (noticed by Andrew)
- Added a new patch to fix the exclusive nature of the IPA limit
[1] https://lore.kernel.org/r/20210308174643.761100-1-maz@kernel.org
[2] https://lore.kernel.org/r/20210310104208.3819061-1-maz@kernel.org
Marc Zyngier (2):
KVM: arm64: Reject VM creation when the default IPA size is
unsupported
KVM: arm64: Fix exclusive limit for IPA size
Documentation/virt/kvm/api.rst | 3 +++
arch/arm64/kvm/mmu.c | 3 +--
arch/arm64/kvm/reset.c | 12 ++++++++----
3 files changed, 12 insertions(+), 6 deletions(-)
--
2.29.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-11 10:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 10:00 Marc Zyngier [this message]
2021-03-11 10:00 ` [PATCH v3 0/2] KVM: arm64: Assorted IPA size fixes Marc Zyngier
2021-03-11 10:00 ` Marc Zyngier
2021-03-11 10:00 ` [PATCH v3 1/2] KVM: arm64: Reject VM creation when the default IPA size is unsupported Marc Zyngier
2021-03-11 10:00 ` Marc Zyngier
2021-03-11 10:00 ` Marc Zyngier
2021-03-11 11:08 ` Andrew Jones
2021-03-11 11:08 ` Andrew Jones
2021-03-11 11:08 ` Andrew Jones
2021-03-11 14:05 ` Auger Eric
2021-03-11 14:05 ` Auger Eric
2021-03-11 14:05 ` Auger Eric
2021-03-11 10:00 ` [PATCH v3 2/2] KVM: arm64: Fix exclusive limit for IPA size Marc Zyngier
2021-03-11 10:00 ` Marc Zyngier
2021-03-11 10:00 ` Marc Zyngier
2021-03-11 11:15 ` Andrew Jones
2021-03-11 11:15 ` Andrew Jones
2021-03-11 11:15 ` Andrew Jones
2021-03-12 15:44 ` Marc Zyngier
2021-03-12 15:44 ` Marc Zyngier
2021-03-12 15:44 ` Marc Zyngier
2021-03-12 16:04 ` [PATCH v3 0/2] KVM: arm64: Assorted IPA size fixes Marc Zyngier
2021-03-12 16:04 ` Marc Zyngier
2021-03-12 16:04 ` 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=20210311100016.3830038-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=suzuki.poulose@arm.com \
--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.