From: Marc Zyngier <maz@kernel.org>
To: qemu-devel@nongnu.org
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel-team@android.com, Andrew Jones <drjones@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [PATCH v4 0/6] target/arm: Reduced-IPA space and highmem fixes
Date: Fri, 7 Jan 2022 16:33:18 +0000 [thread overview]
Message-ID: <20220107163324.2491209-1-maz@kernel.org> (raw)
Here's 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 or PA space restriction.
This series does a few things:
- introduce new attributes to control the enabling of the highmem
GICv3 redistributors and the highmem PCIe MMIO range
- correctly cap the PA range with highmem is off
- generalise the highmem behaviour to any PA range
- disable each highmem device region that doesn't fit in the PA range
- cleanup uses of highmem outside of virt_set_memmap()
This has been tested on an M1-based Mac-mini running Linux v5.16-rc6
with both KVM and TCG.
* From v3 [1]:
- Introduced highmem_mmio as the MMIO pendant to highmem_ecam after
Eric made it plain that I was misguided in using highmem_ecam to
gate the MMIO region.
- Fixed the way the top of RAM is enforced (using the device memory
size, rounded up to the nearest GB). I long debated *not* using
the rounded up version, but finally decided that it would be the
least surprising, given that each slot is supposed to hold a full
GB.
- Now allowing some of the highmem devices to be individually
enabled if they fit in the PA range. For example, a system with a
39bit PA range and at most 255GB of RAM can use the highmem redist
and PCIe ECAM ranges, but not the high PCIe range.
- Dropped some of Andrew's RBs, as the code significantly changed.
[1] https://lore.kernel.org/r/20211227211642.994461-1-maz@kernel.org
Marc Zyngier (6):
hw/arm/virt: Add a control for the the highmem PCIe MMIO
hw/arm/virt: Add a control for the the highmem redistributors
hw/arm/virt: Honor highmem setting when computing the memory map
hw/arm/virt: Use the PA range to compute the memory map
hw/arm/virt: Disable highmem devices that don't fit in the PA range
hw/arm/virt: Drop superfluous checks against highmem
hw/arm/virt-acpi-build.c | 10 ++---
hw/arm/virt.c | 87 +++++++++++++++++++++++++++++++++++-----
include/hw/arm/virt.h | 5 ++-
3 files changed, 85 insertions(+), 17 deletions(-)
--
2.30.2
WARNING: multiple messages have this Message-ID (diff)
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: [PATCH v4 0/6] target/arm: Reduced-IPA space and highmem fixes
Date: Fri, 7 Jan 2022 16:33:18 +0000 [thread overview]
Message-ID: <20220107163324.2491209-1-maz@kernel.org> (raw)
Here's 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 or PA space restriction.
This series does a few things:
- introduce new attributes to control the enabling of the highmem
GICv3 redistributors and the highmem PCIe MMIO range
- correctly cap the PA range with highmem is off
- generalise the highmem behaviour to any PA range
- disable each highmem device region that doesn't fit in the PA range
- cleanup uses of highmem outside of virt_set_memmap()
This has been tested on an M1-based Mac-mini running Linux v5.16-rc6
with both KVM and TCG.
* From v3 [1]:
- Introduced highmem_mmio as the MMIO pendant to highmem_ecam after
Eric made it plain that I was misguided in using highmem_ecam to
gate the MMIO region.
- Fixed the way the top of RAM is enforced (using the device memory
size, rounded up to the nearest GB). I long debated *not* using
the rounded up version, but finally decided that it would be the
least surprising, given that each slot is supposed to hold a full
GB.
- Now allowing some of the highmem devices to be individually
enabled if they fit in the PA range. For example, a system with a
39bit PA range and at most 255GB of RAM can use the highmem redist
and PCIe ECAM ranges, but not the high PCIe range.
- Dropped some of Andrew's RBs, as the code significantly changed.
[1] https://lore.kernel.org/r/20211227211642.994461-1-maz@kernel.org
Marc Zyngier (6):
hw/arm/virt: Add a control for the the highmem PCIe MMIO
hw/arm/virt: Add a control for the the highmem redistributors
hw/arm/virt: Honor highmem setting when computing the memory map
hw/arm/virt: Use the PA range to compute the memory map
hw/arm/virt: Disable highmem devices that don't fit in the PA range
hw/arm/virt: Drop superfluous checks against highmem
hw/arm/virt-acpi-build.c | 10 ++---
hw/arm/virt.c | 87 +++++++++++++++++++++++++++++++++++-----
include/hw/arm/virt.h | 5 ++-
3 files changed, 85 insertions(+), 17 deletions(-)
--
2.30.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: 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: [PATCH v4 0/6] target/arm: Reduced-IPA space and highmem fixes
Date: Fri, 7 Jan 2022 16:33:18 +0000 [thread overview]
Message-ID: <20220107163324.2491209-1-maz@kernel.org> (raw)
Here's 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 or PA space restriction.
This series does a few things:
- introduce new attributes to control the enabling of the highmem
GICv3 redistributors and the highmem PCIe MMIO range
- correctly cap the PA range with highmem is off
- generalise the highmem behaviour to any PA range
- disable each highmem device region that doesn't fit in the PA range
- cleanup uses of highmem outside of virt_set_memmap()
This has been tested on an M1-based Mac-mini running Linux v5.16-rc6
with both KVM and TCG.
* From v3 [1]:
- Introduced highmem_mmio as the MMIO pendant to highmem_ecam after
Eric made it plain that I was misguided in using highmem_ecam to
gate the MMIO region.
- Fixed the way the top of RAM is enforced (using the device memory
size, rounded up to the nearest GB). I long debated *not* using
the rounded up version, but finally decided that it would be the
least surprising, given that each slot is supposed to hold a full
GB.
- Now allowing some of the highmem devices to be individually
enabled if they fit in the PA range. For example, a system with a
39bit PA range and at most 255GB of RAM can use the highmem redist
and PCIe ECAM ranges, but not the high PCIe range.
- Dropped some of Andrew's RBs, as the code significantly changed.
[1] https://lore.kernel.org/r/20211227211642.994461-1-maz@kernel.org
Marc Zyngier (6):
hw/arm/virt: Add a control for the the highmem PCIe MMIO
hw/arm/virt: Add a control for the the highmem redistributors
hw/arm/virt: Honor highmem setting when computing the memory map
hw/arm/virt: Use the PA range to compute the memory map
hw/arm/virt: Disable highmem devices that don't fit in the PA range
hw/arm/virt: Drop superfluous checks against highmem
hw/arm/virt-acpi-build.c | 10 ++---
hw/arm/virt.c | 87 +++++++++++++++++++++++++++++++++++-----
include/hw/arm/virt.h | 5 ++-
3 files changed, 85 insertions(+), 17 deletions(-)
--
2.30.2
next reply other threads:[~2022-01-07 16:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 16:33 Marc Zyngier [this message]
2022-01-07 16:33 ` [PATCH v4 0/6] target/arm: Reduced-IPA space and highmem fixes Marc Zyngier
2022-01-07 16:33 ` 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 ` Marc Zyngier
2022-01-07 16:33 ` 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-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-10 15:35 ` Eric Auger
2022-01-10 15:35 ` Eric Auger
2022-01-10 15:35 ` Eric Auger
2022-01-10 15:45 ` Marc Zyngier
2022-01-10 15:45 ` Marc Zyngier
2022-01-10 15:45 ` Marc Zyngier
2022-01-10 15:47 ` Peter Maydell
2022-01-10 15:47 ` Peter Maydell
2022-01-10 15:47 ` Peter Maydell
2022-01-10 16:02 ` Marc Zyngier
2022-01-10 16:02 ` Marc Zyngier
2022-01-10 16:02 ` Marc Zyngier
2022-01-10 15:48 ` Eric Auger
2022-01-10 15:48 ` Eric Auger
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-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-10 15:30 ` Eric Auger
2022-01-10 15:30 ` Eric Auger
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-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-10 15:38 ` Eric Auger
2022-01-10 15:38 ` Eric Auger
2022-01-10 15:38 ` Eric Auger
2022-01-10 15:58 ` Marc Zyngier
2022-01-10 15:58 ` Marc Zyngier
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-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-10 17:12 ` Eric Auger
2022-01-10 17:12 ` Eric Auger
2022-01-10 17:12 ` Eric Auger
2022-01-10 18:51 ` Marc Zyngier
2022-01-10 18:51 ` Marc Zyngier
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-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-10 17:14 ` Eric Auger
2022-01-10 17:14 ` Eric Auger
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=20220107163324.2491209-1-maz@kernel.org \
--to=maz@kernel.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=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 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.