summaryrefslogtreecommitdiff
path: root/target-ppc/cpu.h
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2012-09-20 17:42:27 +0000
committerAlexander Graf <agraf@suse.de>2012-10-04 15:54:18 +0200
commit382be75df77142cf6bdc7f5852738029eeb9e23a (patch)
treed60dfdc6c089f97ee965cb42d7488ea5164f95af /target-ppc/cpu.h
parent35f9304d925a5423c51bd2c83a81fa3cc2b6e680 (diff)
downloadqemu-382be75df77142cf6bdc7f5852738029eeb9e23a.tar.gz
qemu-382be75df77142cf6bdc7f5852738029eeb9e23a.tar.bz2
qemu-382be75df77142cf6bdc7f5852738029eeb9e23a.zip
pseries: Set hash table size based on RAM size
Currently the pseries machine code always attempts to set the size of the guests's hash page table to 16MB. However, because of the way the POWER MMU works, a suitable hash page table size should really depend on memory size. 16MB will be excessive for guests with <1GB and RAM, and may not be enough for guests with >2GB of RAM (depending on guest page size and other factors). The usual given rule of thumb is that the hash table should be 1/64 of the size of memory, but in fact the Linux guests we are aiming at don't really need that much. This patch, therefore, changes the hash table allocation code to aim for 1/128 of the size of RAM (rounding up). When using KVM, this size may still be adjusted by the host kernel if it is unable to allocate a suitable (contiguous) table. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'target-ppc/cpu.h')
0 files changed, 0 insertions, 0 deletions