diff options
| author | Christian Borntraeger <[email protected]> | 2009-06-23 17:24:06 +0200 |
|---|---|---|
| committer | Avi Kivity <[email protected]> | 2009-09-10 08:33:01 +0300 |
| commit | 3eea8437f61ca1f9192d146124425e759c3e5758 (patch) | |
| tree | ae32ee0c2b33c0fc771a9ff3f7519ef2f6e8b9af /scripts/patch-kernel | |
| parent | 4668f050787015805a7e8ea29cc4f81d8f07cedb (diff) | |
KVM: s390: Fix memslot initialization for userspace_addr != 0
Since
commit 854b5338196b1175706e99d63be43a4f8d8ab607
Author: Christian Ehrhardt <[email protected]>
KVM: s390: streamline memslot handling
s390 uses the values of the memslot instead of doing everything in the arch
ioctl handler of the KVM_SET_USER_MEMORY_REGION. Unfortunately we missed to
set the userspace_addr of our memslot due to our s390 ifdef in
__kvm_set_memory_region.
Old s390 userspace launchers did not notice, since they started the guest at
userspace address 0.
Because of CONFIG_DEFAULT_MMAP_MIN_ADDR we now put the guest at 1M userspace,
which does not work. This patch makes sure that new.userspace_addr is set
on s390.
This fix should go in quickly. Nevertheless, looking at the code we should
clean up that ifdef in the long term. Any kernel janitors?
Signed-off-by: Christian Borntraeger <[email protected]>
Signed-off-by: Avi Kivity <[email protected]>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions