diff options
author | Heiko Carstens <heiko.carstens@de.ibm.com> | 2011-01-17 15:21:08 -0500 |
---|---|---|
committer | Marcelo Tosatti <mtosatti@redhat.com> | 2011-03-17 12:08:26 -0400 |
commit | d48ead8b0b48862a87138d04efb7580a1a25beb5 (patch) | |
tree | 7254bd3f2e3b16211e8ca821474d1049aed625c2 /virt | |
parent | 9ca523183166343fde060e2198237bb345b8a77d (diff) |
KVM: fix build warning within __kvm_set_memory_region() on s390
Get rid of this warning:
CC arch/s390/kvm/../../../virt/kvm/kvm_main.o
arch/s390/kvm/../../../virt/kvm/kvm_main.c:596:12: warning: 'kvm_create_dirty_bitmap' defined but not used
The only caller of the function is within a !CONFIG_S390 section, so add the
same ifdef around kvm_create_dirty_bitmap() as well.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'virt')
-rw-r--r-- | virt/kvm/kvm_main.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c index a3a8f5fb369e..fd67bcde9980 100644 --- a/virt/kvm/kvm_main.c +++ b/virt/kvm/kvm_main.c | |||
@@ -588,6 +588,7 @@ static int kvm_vm_release(struct inode *inode, struct file *filp) | |||
588 | return 0; | 588 | return 0; |
589 | } | 589 | } |
590 | 590 | ||
591 | #ifndef CONFIG_S390 | ||
591 | /* | 592 | /* |
592 | * Allocation size is twice as large as the actual dirty bitmap size. | 593 | * Allocation size is twice as large as the actual dirty bitmap size. |
593 | * This makes it possible to do double buffering: see x86's | 594 | * This makes it possible to do double buffering: see x86's |
@@ -608,6 +609,7 @@ static int kvm_create_dirty_bitmap(struct kvm_memory_slot *memslot) | |||
608 | memslot->dirty_bitmap_head = memslot->dirty_bitmap; | 609 | memslot->dirty_bitmap_head = memslot->dirty_bitmap; |
609 | return 0; | 610 | return 0; |
610 | } | 611 | } |
612 | #endif /* !CONFIG_S390 */ | ||
611 | 613 | ||
612 | /* | 614 | /* |
613 | * Allocate some memory and give it an address in the guest physical address | 615 | * Allocate some memory and give it an address in the guest physical address |