1 /* 2 * Declarations for cpu physical memory functions 3 * 4 * Copyright 2011 Red Hat, Inc. and/or its affiliates 5 * 6 * Authors: 7 * Avi Kivity <avi@redhat.com> 8 * 9 * This work is licensed under the terms of the GNU GPL, version 2 or 10 * later. See the COPYING file in the top-level directory. 11 * 12 */ 13 14 /* 15 * This header is for use by exec.c and memory.c ONLY. Do not include it. 16 * The functions declared here will be removed soon. 17 */ 18 19 #ifndef QEMU_EXEC_RAMBLOCK_H 20 #define QEMU_EXEC_RAMBLOCK_H 21 22 #ifndef CONFIG_USER_ONLY 23 #include "cpu-common.h" 24 #include "qemu/rcu.h" 25 #include "exec/ramlist.h" 26 27 struct RAMBlock { 28 struct rcu_head rcu; 29 struct MemoryRegion *mr; 30 uint8_t *host; 31 uint8_t *colo_cache; /* For colo, VM's ram cache */ 32 ram_addr_t offset; 33 ram_addr_t used_length; 34 ram_addr_t max_length; 35 void (*resized)(const char*, uint64_t length, void *host); 36 uint32_t flags; 37 /* Protected by iothread lock. */ 38 char idstr[256]; 39 /* RCU-enabled, writes protected by the ramlist lock */ 40 QLIST_ENTRY(RAMBlock) next; 41 QLIST_HEAD(, RAMBlockNotifier) ramblock_notifiers; 42 int fd; 43 size_t page_size; 44 /* dirty bitmap used during migration */ 45 unsigned long *bmap; 46 /* bitmap of already received pages in postcopy */ 47 unsigned long *receivedmap; 48 49 /* 50 * bitmap to track already cleared dirty bitmap. When the bit is 51 * set, it means the corresponding memory chunk needs a log-clear. 52 * Set this up to non-NULL to enable the capability to postpone 53 * and split clearing of dirty bitmap on the remote node (e.g., 54 * KVM). The bitmap will be set only when doing global sync. 55 * 56 * NOTE: this bitmap is different comparing to the other bitmaps 57 * in that one bit can represent multiple guest pages (which is 58 * decided by the `clear_bmap_shift' variable below). On 59 * destination side, this should always be NULL, and the variable 60 * `clear_bmap_shift' is meaningless. 61 */ 62 unsigned long *clear_bmap; 63 uint8_t clear_bmap_shift; 64 65 /* 66 * RAM block length that corresponds to the used_length on the migration 67 * source (after RAM block sizes were synchronized). Especially, after 68 * starting to run the guest, used_length and postcopy_length can differ. 69 * Used to register/unregister uffd handlers and as the size of the received 70 * bitmap. Receiving any page beyond this length will bail out, as it 71 * could not have been valid on the source. 72 */ 73 ram_addr_t postcopy_length; 74 }; 75 #endif 76 #endif 77