KVM: page track: add the framework of guest page tracking
The array, gfn_track[mode][gfn], is introduced in memory slot for every
guest page, this is the tracking count for the gust page on different
modes. If the page is tracked then the count is increased, the page is
not tracked after the count reaches zero
We use 'unsigned short' as the tracking count which should be enough as
shadow page table only can use 2^14 (2^3 for level, 2^1 for cr4_pae, 2^2
for quadrant, 2^3 for access, 2^1 for nxe, 2^1 for cr0_wp, 2^1 for
smep_andnot_wp, 2^1 for smap_andnot_wp, and 2^1 for smm) at most, there
is enough room for other trackers
Two callbacks, kvm_page_track_create_memslot() and
kvm_page_track_free_memslot() are implemented in this patch, they are
internally used to initialize and reclaim the memory of the array
Currently, only write track mode is supported
Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-02-24 09:51:09 +00:00
|
|
|
#ifndef _ASM_X86_KVM_PAGE_TRACK_H
|
|
|
|
#define _ASM_X86_KVM_PAGE_TRACK_H
|
|
|
|
|
|
|
|
enum kvm_page_track_mode {
|
|
|
|
KVM_PAGE_TRACK_WRITE,
|
|
|
|
KVM_PAGE_TRACK_MAX,
|
|
|
|
};
|
|
|
|
|
2016-02-24 09:51:13 +00:00
|
|
|
/*
|
|
|
|
* The notifier represented by @kvm_page_track_notifier_node is linked into
|
|
|
|
* the head which will be notified when guest is triggering the track event.
|
|
|
|
*
|
|
|
|
* Write access on the head is protected by kvm->mmu_lock, read access
|
|
|
|
* is protected by track_srcu.
|
|
|
|
*/
|
|
|
|
struct kvm_page_track_notifier_head {
|
|
|
|
struct srcu_struct track_srcu;
|
|
|
|
struct hlist_head track_notifier_list;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct kvm_page_track_notifier_node {
|
|
|
|
struct hlist_node node;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* It is called when guest is writing the write-tracked page
|
|
|
|
* and write emulation is finished at that time.
|
|
|
|
*
|
|
|
|
* @vcpu: the vcpu where the write access happened.
|
|
|
|
* @gpa: the physical address written by guest.
|
|
|
|
* @new: the data was written to the address.
|
|
|
|
* @bytes: the written length.
|
|
|
|
*/
|
|
|
|
void (*track_write)(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,
|
|
|
|
int bytes);
|
2016-10-09 07:41:44 +00:00
|
|
|
/*
|
|
|
|
* It is called when memory slot is being moved or removed
|
|
|
|
* users can drop write-protection for the pages in that memory slot
|
|
|
|
*
|
|
|
|
* @kvm: the kvm where memory slot being moved or removed
|
|
|
|
* @slot: the memory slot being moved or removed
|
|
|
|
*/
|
|
|
|
void (*track_flush_slot)(struct kvm *kvm, struct kvm_memory_slot *slot);
|
2016-02-24 09:51:13 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
void kvm_page_track_init(struct kvm *kvm);
|
|
|
|
|
KVM: page track: add the framework of guest page tracking
The array, gfn_track[mode][gfn], is introduced in memory slot for every
guest page, this is the tracking count for the gust page on different
modes. If the page is tracked then the count is increased, the page is
not tracked after the count reaches zero
We use 'unsigned short' as the tracking count which should be enough as
shadow page table only can use 2^14 (2^3 for level, 2^1 for cr4_pae, 2^2
for quadrant, 2^3 for access, 2^1 for nxe, 2^1 for cr0_wp, 2^1 for
smep_andnot_wp, 2^1 for smap_andnot_wp, and 2^1 for smm) at most, there
is enough room for other trackers
Two callbacks, kvm_page_track_create_memslot() and
kvm_page_track_free_memslot() are implemented in this patch, they are
internally used to initialize and reclaim the memory of the array
Currently, only write track mode is supported
Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-02-24 09:51:09 +00:00
|
|
|
void kvm_page_track_free_memslot(struct kvm_memory_slot *free,
|
|
|
|
struct kvm_memory_slot *dont);
|
|
|
|
int kvm_page_track_create_memslot(struct kvm_memory_slot *slot,
|
|
|
|
unsigned long npages);
|
2016-02-24 09:51:10 +00:00
|
|
|
|
|
|
|
void kvm_slot_page_track_add_page(struct kvm *kvm,
|
|
|
|
struct kvm_memory_slot *slot, gfn_t gfn,
|
|
|
|
enum kvm_page_track_mode mode);
|
|
|
|
void kvm_slot_page_track_remove_page(struct kvm *kvm,
|
|
|
|
struct kvm_memory_slot *slot, gfn_t gfn,
|
|
|
|
enum kvm_page_track_mode mode);
|
2016-02-24 09:51:11 +00:00
|
|
|
bool kvm_page_track_is_active(struct kvm_vcpu *vcpu, gfn_t gfn,
|
|
|
|
enum kvm_page_track_mode mode);
|
2016-02-24 09:51:13 +00:00
|
|
|
|
|
|
|
void
|
|
|
|
kvm_page_track_register_notifier(struct kvm *kvm,
|
|
|
|
struct kvm_page_track_notifier_node *n);
|
|
|
|
void
|
|
|
|
kvm_page_track_unregister_notifier(struct kvm *kvm,
|
|
|
|
struct kvm_page_track_notifier_node *n);
|
|
|
|
void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,
|
|
|
|
int bytes);
|
2016-10-09 07:41:44 +00:00
|
|
|
void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot);
|
KVM: page track: add the framework of guest page tracking
The array, gfn_track[mode][gfn], is introduced in memory slot for every
guest page, this is the tracking count for the gust page on different
modes. If the page is tracked then the count is increased, the page is
not tracked after the count reaches zero
We use 'unsigned short' as the tracking count which should be enough as
shadow page table only can use 2^14 (2^3 for level, 2^1 for cr4_pae, 2^2
for quadrant, 2^3 for access, 2^1 for nxe, 2^1 for cr0_wp, 2^1 for
smep_andnot_wp, 2^1 for smap_andnot_wp, and 2^1 for smm) at most, there
is enough room for other trackers
Two callbacks, kvm_page_track_create_memslot() and
kvm_page_track_free_memslot() are implemented in this patch, they are
internally used to initialize and reclaim the memory of the array
Currently, only write track mode is supported
Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-02-24 09:51:09 +00:00
|
|
|
#endif
|