aboutsummaryrefslogtreecommitdiff
path: root/target-ppc/mmu-hash32.c
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2016-02-09 10:21:56 +1000
committerDavid Gibson <david@gibson.dropbear.id.au>2016-02-17 09:59:30 +1100
commitc5f54f3e31bf693f70a98d4d73ea5dbe05689857 (patch)
treefb01e25c00c361cdaf3cbb85d7b66db704d48ac9 /target-ppc/mmu-hash32.c
parent8dfe8e7f4facef400ef1c220f29196ae5cfc526c (diff)
downloadqemu-c5f54f3e31bf693f70a98d4d73ea5dbe05689857.zip
qemu-c5f54f3e31bf693f70a98d4d73ea5dbe05689857.tar.gz
qemu-c5f54f3e31bf693f70a98d4d73ea5dbe05689857.tar.bz2
pseries: Move hash page table allocation to reset time
At the moment the size of the hash page table (HPT) is fixed based on the maximum memory allowed to the guest. As such, we allocate the table during machine construction, and just clear it at reset. However, we're planning to implement a PAPR extension allowing the hash page table to be resized at runtime. This will mean that on reset we want to revert it to the default size. It also means that when migrating, we need to make sure the destination allocates an HPT of size matching the host, since the guest could have changed it before the migration. This patch replaces the spapr_alloc_htab() and spapr_reset_htab() functions with a new spapr_reallocate_hpt() function. This is called at reset and inbound migration only, not during machine init any more. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Diffstat (limited to 'target-ppc/mmu-hash32.c')
0 files changed, 0 insertions, 0 deletions