On Thu, 2007-11-15 at 23:21 +0800, Zhang, Xiantao wrote: > Currently, KVM_SET_MEMORY_REGION ioctl is put under arch, but its > implementation is in common code . From code logic, it seems very > strange. Maybe I missed some threads about its discuss, who can tell me > the story ? Thanks a lot! :) > Xiantao
kvm x86 have 2 ways to create memory one old way: allocate the memory inside the kernel one new way: allocate the memory inside userspace and send a address to the kernel the ioctl that call to allocate memory inside the kernel is: KVM_SET_MEMORY_REGION and the one that allocate the memory in userspace is: KVM_SET_USER_MEMORY_REGION all the ports of kvm to other architactures will use the KVM_SET_USER_MEMORY_REGION, and KVM_SET_MEMORY_REGION is left just for legacy support for older userspace (checkout KVM_SET_USER_MEMORY_REGION, it is in the common code) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
