From: Marc Zyngier <maz@kernel.org>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, kernel-team@android.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 0/3] target/arm: Reduced-IPA space and highmem=off fixes
Date: Sun, 22 Aug 2021 15:48:49 +0100 [thread overview]
Message-ID: <5ae02b70fcb1df96306f96eddae28486@kernel.org> (raw)
In-Reply-To: <20210822144441.1290891-1-maz@kernel.org>
On 2021-08-22 15:44, Marc Zyngier wrote:
> With the availability of a fruity range of arm64 systems, it becomes
> obvious that QEMU doesn't deal very well with limited IPA ranges when
> used as a front-end for KVM.
>
> This short series aims at making usable on such systems:
> - the first patch makes the creation of a scratch VM IPA-limit aware
> - the second one actually removes the highmem devices from the
> computed IPA range when highmem=off
> - the last one addresses an imprecision in the documentation for the
> highmem option
>
> This has been tested on an M1-based Mac-mini running Linux v5.14-rc6.
I realise I haven't been very clear in my description of the above.
With this series, using 'highmem=off' results in a usable VM, while
sticking to the default 'highmem=on' still generates an error.
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
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: qemu-devel@nongnu.org
Cc: Andrew Jones <drjones@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH 0/3] target/arm: Reduced-IPA space and highmem=off fixes
Date: Sun, 22 Aug 2021 15:48:49 +0100 [thread overview]
Message-ID: <5ae02b70fcb1df96306f96eddae28486@kernel.org> (raw)
In-Reply-To: <20210822144441.1290891-1-maz@kernel.org>
On 2021-08-22 15:44, Marc Zyngier wrote:
> With the availability of a fruity range of arm64 systems, it becomes
> obvious that QEMU doesn't deal very well with limited IPA ranges when
> used as a front-end for KVM.
>
> This short series aims at making usable on such systems:
> - the first patch makes the creation of a scratch VM IPA-limit aware
> - the second one actually removes the highmem devices from the
> computed IPA range when highmem=off
> - the last one addresses an imprecision in the documentation for the
> highmem option
>
> This has been tested on an M1-based Mac-mini running Linux v5.14-rc6.
I realise I haven't been very clear in my description of the above.
With this series, using 'highmem=off' results in a usable VM, while
sticking to the default 'highmem=on' still generates an error.
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
kvm@vger.kernel.org, Eric Auger <eric.auger@redhat.com>,
kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 0/3] target/arm: Reduced-IPA space and highmem=off fixes
Date: Sun, 22 Aug 2021 15:48:49 +0100 [thread overview]
Message-ID: <5ae02b70fcb1df96306f96eddae28486@kernel.org> (raw)
In-Reply-To: <20210822144441.1290891-1-maz@kernel.org>
On 2021-08-22 15:44, Marc Zyngier wrote:
> With the availability of a fruity range of arm64 systems, it becomes
> obvious that QEMU doesn't deal very well with limited IPA ranges when
> used as a front-end for KVM.
>
> This short series aims at making usable on such systems:
> - the first patch makes the creation of a scratch VM IPA-limit aware
> - the second one actually removes the highmem devices from the
> computed IPA range when highmem=off
> - the last one addresses an imprecision in the documentation for the
> highmem option
>
> This has been tested on an M1-based Mac-mini running Linux v5.14-rc6.
I realise I haven't been very clear in my description of the above.
With this series, using 'highmem=off' results in a usable VM, while
sticking to the default 'highmem=on' still generates an error.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2021-08-22 14:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 14:44 [PATCH 0/3] target/arm: Reduced-IPA space and highmem=off fixes Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-08-22 14:44 ` [PATCH 1/3] hw/arm/virt: KVM: Probe for KVM_CAP_ARM_VM_IPA_SIZE when creating scratch VM Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-08-23 9:07 ` Andrew Jones
2021-08-23 9:07 ` Andrew Jones
2021-08-23 9:07 ` Andrew Jones
2021-09-08 7:16 ` Eric Auger
2021-09-08 7:16 ` Eric Auger
2021-09-08 7:16 ` Eric Auger
2021-08-22 14:44 ` [PATCH 2/3] hw/arm/virt: Honor highmem setting when computing highest_gpa Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-09-07 12:58 ` Peter Maydell
2021-09-07 12:58 ` Peter Maydell
2021-09-07 12:58 ` Peter Maydell
2021-09-08 7:16 ` Eric Auger
2021-09-08 7:16 ` Eric Auger
2021-09-08 7:16 ` Eric Auger
2021-08-22 14:44 ` [PATCH 3/3] docs/system/arm/virt: Fix documentation for the 'highmem' option Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-08-22 14:44 ` Marc Zyngier
2021-09-07 12:51 ` Peter Maydell
2021-09-07 12:51 ` Peter Maydell
2021-09-07 12:51 ` Peter Maydell
2021-09-07 17:09 ` Marc Zyngier
2021-09-07 17:09 ` Marc Zyngier
2021-09-07 17:09 ` Marc Zyngier
2021-09-07 18:25 ` Peter Maydell
2021-09-07 18:25 ` Peter Maydell
2021-09-07 18:25 ` Peter Maydell
2021-09-08 9:16 ` Marc Zyngier
2021-09-08 9:16 ` Marc Zyngier
2021-09-08 9:16 ` Marc Zyngier
2021-09-08 8:53 ` Eric Auger
2021-09-08 8:53 ` Eric Auger
2021-09-08 8:53 ` Eric Auger
2021-08-22 14:48 ` Marc Zyngier [this message]
2021-08-22 14:48 ` [PATCH 0/3] target/arm: Reduced-IPA space and highmem=off fixes Marc Zyngier
2021-08-22 14:48 ` Marc Zyngier
2021-09-07 12:52 ` Peter Maydell
2021-09-07 12:52 ` Peter Maydell
2021-09-07 12:52 ` Peter Maydell
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=5ae02b70fcb1df96306f96eddae28486@kernel.org \
--to=maz@kernel.org \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=qemu-devel@nongnu.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.