diff options
author | Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> | 2013-02-07 18:55:57 +0900 |
---|---|---|
committer | Gleb Natapov <gleb@redhat.com> | 2013-02-11 11:52:00 +0200 |
commit | 7a905b1485adf863607b5fc9e32a3fa3838bcc23 (patch) | |
tree | 8f61239e5d74bd58e9972bdc4da27e01fd725419 /crypto | |
parent | 257090f70233084488f7b3ebe99be8c159a23281 (diff) | |
download | linux-stable-7a905b1485adf863607b5fc9e32a3fa3838bcc23.tar.gz linux-stable-7a905b1485adf863607b5fc9e32a3fa3838bcc23.tar.bz2 linux-stable-7a905b1485adf863607b5fc9e32a3fa3838bcc23.zip |
KVM: Remove user_alloc from struct kvm_memory_slot
This field was needed to differentiate memory slots created by the new
API, KVM_SET_USER_MEMORY_REGION, from those by the old equivalent,
KVM_SET_MEMORY_REGION, whose support was dropped long before:
commit b74a07beed0e64bfba413dcb70dd6749c57f43dc
KVM: Remove kernel-allocated memory regions
Although we also have private memory slots to which KVM allocates
memory with vm_mmap(), !user_alloc slots in other words, the slot id
should be enough for differentiating them.
Note: corresponding function parameters will be removed later.
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions