From: Eric Auger <eric.auger@redhat.com>
To: Marc Zyngier <maz@kernel.org>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
kernel-team@android.com, kvmarm@lists.cs.columbia.edu,
kvm@vger.kernel.org
Subject: Re: [PATCH v4 3/6] hw/arm/virt: Honor highmem setting when computing the memory map
Date: Mon, 10 Jan 2022 16:30:58 +0100 [thread overview]
Message-ID: <a72846d6-d559-9f12-154f-20c04821747e@redhat.com> (raw)
In-Reply-To: <20220107163324.2491209-4-maz@kernel.org>
Hi Marc,
On 1/7/22 5:33 PM, Marc Zyngier wrote:
> Even when the VM is configured with highmem=off, the highest_gpa
> field includes devices that are above the 4GiB limit.
> Similarily, nothing seem to check that the memory is within
> the limit set by the highmem=off option.
>
> This leads to failures in virt_kvm_type() on systems that have
> a crippled IPA range, as the reported IPA space is larger than
> what it should be.
>
> Instead, honor the user-specified limit to only use the devices
> at the lowest end of the spectrum, and fail if we have memory
> crossing the 4GiB limit.
>
> Reviewed-by: Andrew Jones <drjones@redhat.com>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Eric
> ---
> hw/arm/virt.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index 4d1d629432..57c55e8a37 100644
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -1663,7 +1663,7 @@ static uint64_t virt_cpu_mp_affinity(VirtMachineState *vms, int idx)
> static void virt_set_memmap(VirtMachineState *vms)
> {
> MachineState *ms = MACHINE(vms);
> - hwaddr base, device_memory_base, device_memory_size;
> + hwaddr base, device_memory_base, device_memory_size, memtop;
> int i;
>
> vms->memmap = extended_memmap;
> @@ -1690,7 +1690,11 @@ static void virt_set_memmap(VirtMachineState *vms)
> device_memory_size = ms->maxram_size - ms->ram_size + ms->ram_slots * GiB;
>
> /* Base address of the high IO region */
> - base = device_memory_base + ROUND_UP(device_memory_size, GiB);
> + memtop = base = device_memory_base + ROUND_UP(device_memory_size, GiB);
> + if (!vms->highmem && memtop > 4 * GiB) {
> + error_report("highmem=off, but memory crosses the 4GiB limit\n");
> + exit(EXIT_FAILURE);
> + }
> if (base < device_memory_base) {
> error_report("maxmem/slots too huge");
> exit(EXIT_FAILURE);
> @@ -1707,7 +1711,7 @@ static void virt_set_memmap(VirtMachineState *vms)
> vms->memmap[i].size = size;
> base += size;
> }
> - vms->highest_gpa = base - 1;
> + vms->highest_gpa = (vms->highmem ? base : memtop) - 1;
> if (device_memory_size > 0) {
> ms->device_memory = g_malloc0(sizeof(*ms->device_memory));
> ms->device_memory->base = device_memory_base;
next prev parent reply other threads:[~2022-01-10 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 16:33 [PATCH v4 0/6] target/arm: Reduced-IPA space and highmem fixes Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 1/6] hw/arm/virt: Add a control for the the highmem PCIe MMIO Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 2/6] hw/arm/virt: Add a control for the the highmem redistributors Marc Zyngier
2022-01-10 15:35 ` Eric Auger
2022-01-10 15:45 ` Marc Zyngier
2022-01-10 15:47 ` Peter Maydell
2022-01-10 16:02 ` Marc Zyngier
2022-01-10 15:48 ` Eric Auger
2022-01-07 16:33 ` [PATCH v4 3/6] hw/arm/virt: Honor highmem setting when computing the memory map Marc Zyngier
2022-01-10 15:30 ` Eric Auger [this message]
2022-01-07 16:33 ` [PATCH v4 4/6] hw/arm/virt: Use the PA range to compute " Marc Zyngier
2022-01-10 15:38 ` Eric Auger
2022-01-10 15:58 ` Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 5/6] hw/arm/virt: Disable highmem devices that don't fit in the PA range Marc Zyngier
2022-01-10 17:12 ` Eric Auger
2022-01-10 18:51 ` Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 6/6] hw/arm/virt: Drop superfluous checks against highmem Marc Zyngier
2022-01-10 17:14 ` Eric Auger
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=a72846d6-d559-9f12-154f-20c04821747e@redhat.com \
--to=eric.auger@redhat.com \
--cc=drjones@redhat.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=peter.maydell@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).