From: Peter Maydell <peter.maydell@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: qemu-devel@nongnu.org, Andrew Jones <drjones@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v5 0/6] target/arm: Reduced-IPA space and highmem fixes
Date: Tue, 18 Jan 2022 17:17:57 +0000 [thread overview]
Message-ID: <CAFEAcA9dFVUY5a9WANrS1UEPrbsUueYaUzneMYhjdn=XTKDGvA@mail.gmail.com> (raw)
In-Reply-To: <20220114140741.1358263-1-maz@kernel.org>
On Fri, 14 Jan 2022 at 14:08, Marc Zyngier <maz@kernel.org> wrote:
>
> Here's yet another stab at enabling QEMU on systems with
> pathologically reduced IPA ranges such as the Apple M1 (previous
> version at [1]). Eventually, we're able to run a KVM guest with more
> than just 3GB of RAM on a system with a 36bit IPA space, and at most
> 123 vCPUs.
>
> This also addresses some pathological QEMU behaviours, where the
> highmem property is used as a flag allowing exposure of devices that
> can't possibly fit in the PA space of the VM, resulting in a guest
> failure.
>
> In the end, we generalise the notion of PA space when exposing
> individual devices in the expanded memory map, and treat highmem as
> another flavour of PA space restriction.
Applied to target-arm.next, thanks.
-- PMM
WARNING: multiple messages have this Message-ID (diff)
From: Peter Maydell <peter.maydell@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v5 0/6] target/arm: Reduced-IPA space and highmem fixes
Date: Tue, 18 Jan 2022 17:17:57 +0000 [thread overview]
Message-ID: <CAFEAcA9dFVUY5a9WANrS1UEPrbsUueYaUzneMYhjdn=XTKDGvA@mail.gmail.com> (raw)
In-Reply-To: <20220114140741.1358263-1-maz@kernel.org>
On Fri, 14 Jan 2022 at 14:08, Marc Zyngier <maz@kernel.org> wrote:
>
> Here's yet another stab at enabling QEMU on systems with
> pathologically reduced IPA ranges such as the Apple M1 (previous
> version at [1]). Eventually, we're able to run a KVM guest with more
> than just 3GB of RAM on a system with a 36bit IPA space, and at most
> 123 vCPUs.
>
> This also addresses some pathological QEMU behaviours, where the
> highmem property is used as a flag allowing exposure of devices that
> can't possibly fit in the PA space of the VM, resulting in a guest
> failure.
>
> In the end, we generalise the notion of PA space when exposing
> individual devices in the expanded memory map, and treat highmem as
> another flavour of PA space restriction.
Applied to target-arm.next, thanks.
-- PMM
_______________________________________________
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: Peter Maydell <peter.maydell@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Andrew Jones <drjones@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Eric Auger <eric.auger@redhat.com>,
kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v5 0/6] target/arm: Reduced-IPA space and highmem fixes
Date: Tue, 18 Jan 2022 17:17:57 +0000 [thread overview]
Message-ID: <CAFEAcA9dFVUY5a9WANrS1UEPrbsUueYaUzneMYhjdn=XTKDGvA@mail.gmail.com> (raw)
In-Reply-To: <20220114140741.1358263-1-maz@kernel.org>
On Fri, 14 Jan 2022 at 14:08, Marc Zyngier <maz@kernel.org> wrote:
>
> Here's yet another stab at enabling QEMU on systems with
> pathologically reduced IPA ranges such as the Apple M1 (previous
> version at [1]). Eventually, we're able to run a KVM guest with more
> than just 3GB of RAM on a system with a 36bit IPA space, and at most
> 123 vCPUs.
>
> This also addresses some pathological QEMU behaviours, where the
> highmem property is used as a flag allowing exposure of devices that
> can't possibly fit in the PA space of the VM, resulting in a guest
> failure.
>
> In the end, we generalise the notion of PA space when exposing
> individual devices in the expanded memory map, and treat highmem as
> another flavour of PA space restriction.
Applied to target-arm.next, thanks.
-- PMM
next prev parent reply other threads:[~2022-01-18 17:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:07 [PATCH v5 0/6] target/arm: Reduced-IPA space and highmem fixes Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` [PATCH v5 1/6] hw/arm/virt: Add a control for the the highmem PCIe MMIO Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-18 13:52 ` Eric Auger
2022-01-18 13:52 ` Eric Auger
2022-01-18 13:52 ` Eric Auger
2022-01-14 14:07 ` [PATCH v5 2/6] hw/arm/virt: Add a control for the the highmem redistributors Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-18 13:51 ` Eric Auger
2022-01-18 13:51 ` Eric Auger
2022-01-18 13:51 ` Eric Auger
2022-01-14 14:07 ` [PATCH v5 3/6] hw/arm/virt: Honor highmem setting when computing the memory map Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` [PATCH v5 4/6] hw/arm/virt: Use the PA range to compute " Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-18 13:51 ` Eric Auger
2022-01-18 13:51 ` Eric Auger
2022-01-18 13:51 ` Eric Auger
2022-01-14 14:07 ` [PATCH v5 5/6] hw/arm/virt: Disable highmem devices that don't fit in the PA range Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-18 13:51 ` Eric Auger
2022-01-18 13:51 ` Eric Auger
2022-01-18 13:51 ` Eric Auger
2022-01-14 14:07 ` [PATCH v5 6/6] hw/arm/virt: Drop superfluous checks against highmem Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-14 14:07 ` Marc Zyngier
2022-01-18 17:17 ` Peter Maydell [this message]
2022-01-18 17:17 ` [PATCH v5 0/6] target/arm: Reduced-IPA space and highmem fixes Peter Maydell
2022-01-18 17:17 ` 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='CAFEAcA9dFVUY5a9WANrS1UEPrbsUueYaUzneMYhjdn=XTKDGvA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.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 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.