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 5/6] hw/arm/virt: Disable highmem devices that don't fit in the PA range
Date: Mon, 10 Jan 2022 18:12:50 +0100 [thread overview]
Message-ID: <dad34b51-51e2-37cd-44cd-7ca7c4fe6129@redhat.com> (raw)
In-Reply-To: <20220107163324.2491209-6-maz@kernel.org>
Hi Marc,
On 1/7/22 5:33 PM, Marc Zyngier wrote:
> In order to only keep the highmem devices that actually fit in
> the PA range, check their location against the range and update
> highest_gpa if they fit. If they don't, mark them them as disabled.
s/them them/them
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
> hw/arm/virt.c | 34 ++++++++++++++++++++++++++++------
> 1 file changed, 28 insertions(+), 6 deletions(-)
>
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index db4b0636e1..70b4773b3e 100644
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -1711,21 +1711,43 @@ static void virt_set_memmap(VirtMachineState *vms, int pa_bits)
> base = vms->memmap[VIRT_MEM].base + LEGACY_RAMLIMIT_BYTES;
> }
>
> + /* We know for sure that at least the memory fits in the PA space */
> + vms->highest_gpa = memtop - 1;
> +
> for (i = VIRT_LOWMEMMAP_LAST; i < ARRAY_SIZE(extended_memmap); i++) {
> hwaddr size = extended_memmap[i].size;
> + bool fits;
>
> base = ROUND_UP(base, size);
> vms->memmap[i].base = base;
> vms->memmap[i].size = size;
> +
> + /*
> + * Check each device to see if they fit in the PA space,
> + * moving highest_gpa as we go.
> + *
> + * For each device that doesn't fit, disable it.
> + */
> + fits = (base + size) <= BIT_ULL(pa_bits);
> + if (fits) {
> + vms->highest_gpa = MAX(vms->highest_gpa, base + size - 1);
why do you need the MAX()?
> + }
> + switch (i) {
> + case VIRT_HIGH_GIC_REDIST2:
> + vms->highmem_redists &= fits;
> + break;
> + case VIRT_HIGH_PCIE_ECAM:
> + vms->highmem_ecam &= fits;
> + break;
> + case VIRT_HIGH_PCIE_MMIO:
> + vms->highmem_mmio &= fits;
> + break;
> + }
> +
> base += size;
> }
>
> - /*
> - * If base fits within pa_bits, all good. If it doesn't, limit it
> - * to the end of RAM, which is guaranteed to fit within pa_bits.
> - */
> - vms->highest_gpa = (base <= BIT_ULL(pa_bits) ? base : memtop) - 1;
> -
> if (device_memory_size > 0) {
> ms->device_memory = g_malloc0(sizeof(*ms->device_memory));
> ms->device_memory->base = device_memory_base;
Eric
next prev parent reply other threads:[~2022-01-10 17:14 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
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 [this message]
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=dad34b51-51e2-37cd-44cd-7ca7c4fe6129@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).