[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-ppc] [RFC for-2.13 0/7] spapr: Clean up pagesize handling
From: |
David Gibson |
Subject: |
[Qemu-ppc] [RFC for-2.13 0/7] spapr: Clean up pagesize handling |
Date: |
Thu, 19 Apr 2018 16:29:10 +1000 |
Currently the "pseries" machine type will (usually) advertise
different pagesizes to the guest when running under KVM and TCG, which
is not how things are supposed to work.
This comes from poor handling of hardware limitations which mean that
under KVM HV the guest is unable to use pagesizes larger than those
backing the guest's RAM on the host side.
The new scheme turns things around by having an explicit machine
parameter controlling the largest page size that the guest is allowed
to use. This limitation applies regardless of accelerator. When
we're running on KVM HV we ensure that our backing pages are adequate
to supply the requested guest page sizes, rather than adjusting the
guest page sizes based on what KVM can supply.
This means that in order to use hugepages in a PAPR guest it's
necessary to add a "cap-hpt-mps=24" machine parameter as well as
setting the mem-path correctly. This is a bit more work on the user
and/or management side, but results in consistent behaviour so I think
it's worth it.
Longer term, we can also use this parameter to control IOMMU page
sizes. However the restrictions here are even more complicated based
on an intersection of guest, host kernel and hardware capabilities.
This applies on top of my recent series cleaning up the PAPR mode
initialization, which in turn applies on top of my ppc-for-2.13 tree.
David Gibson (7):
spapr: Maximum (HPT) pagesize property
spapr: Use maximum page size capability to simplify memory backend
checking
target/ppc: Add ppc_hash64_filter_pagesizes()
spapr: Add cpu_apply hook to capabilities
spapr: Limit available pagesizes to provide a consistent guest
environment
spapr: Don't rewrite mmu capabilities in KVM mode
spapr_pci: Remove unhelpful pagesize warning
hw/ppc/spapr.c | 18 +++---
hw/ppc/spapr_caps.c | 125 ++++++++++++++++++++++++++++++++++++++++
hw/ppc/spapr_cpu_core.c | 4 ++
hw/ppc/spapr_pci.c | 7 ---
include/hw/ppc/spapr.h | 8 ++-
target/ppc/kvm.c | 149 ++++++++++++++++++++++++------------------------
target/ppc/kvm_ppc.h | 11 +++-
target/ppc/mmu-hash64.c | 59 +++++++++++++++++++
target/ppc/mmu-hash64.h | 3 +
9 files changed, 287 insertions(+), 97 deletions(-)
--
2.14.3
- [Qemu-ppc] [RFC for-2.13 0/7] spapr: Clean up pagesize handling,
David Gibson <=
- [Qemu-ppc] [RFC for-2.13 3/7] target/ppc: Add ppc_hash64_filter_pagesizes(), David Gibson, 2018/04/19
- [Qemu-ppc] [RFC for-2.13 2/7] spapr: Use maximum page size capability to simplify memory backend checking, David Gibson, 2018/04/19
- [Qemu-ppc] [RFC for-2.13 7/7] spapr_pci: Remove unhelpful pagesize warning, David Gibson, 2018/04/19
- [Qemu-ppc] [RFC for-2.13 4/7] spapr: Add cpu_apply hook to capabilities, David Gibson, 2018/04/19
- [Qemu-ppc] [RFC for-2.13 5/7] spapr: Limit available pagesizes to provide a consistent guest environment, David Gibson, 2018/04/19
- [Qemu-ppc] [RFC for-2.13 6/7] spapr: Don't rewrite mmu capabilities in KVM mode, David Gibson, 2018/04/19
- [Qemu-ppc] [RFC for-2.13 1/7] spapr: Maximum (HPT) pagesize property, David Gibson, 2018/04/19
- Re: [Qemu-ppc] [RFC for-2.13 0/7] spapr: Clean up pagesize handling, Andrea Bolognani, 2018/04/19