* Re: A question about KVM_SET_MEMORY_REGION ioctl
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A0466-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
@ 2007-11-15 15:18 ` Izik Eidus
[not found] ` <1195139900.17876.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-11-15 15:31 ` Avi Kivity
1 sibling, 1 reply; 4+ messages in thread
From: Izik Eidus @ 2007-11-15 15:18 UTC (permalink / raw)
To: Zhang, Xiantao
Cc: carsteno-tA70FqPdS9bQT0dZR+AlfA,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Hollis Blanchard,
Avi Kivity
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* A question about KVM_SET_MEMORY_REGION ioctl
@ 2007-11-15 15:21 Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A0466-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
0 siblings, 1 reply; 4+ messages in thread
From: Zhang, Xiantao @ 2007-11-15 15:21 UTC (permalink / raw)
To: Avi Kivity, carsteno-tA70FqPdS9bQT0dZR+AlfA, Hollis Blanchard
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
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
-------------------------------------------------------------------------
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: A question about KVM_SET_MEMORY_REGION ioctl
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A0466-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-15 15:18 ` Izik Eidus
@ 2007-11-15 15:31 ` Avi Kivity
1 sibling, 0 replies; 4+ messages in thread
From: Avi Kivity @ 2007-11-15 15:31 UTC (permalink / raw)
To: Zhang, Xiantao
Cc: carsteno-tA70FqPdS9bQT0dZR+AlfA,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Hollis Blanchard
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! :)
>
KVM_SET_MEMORY_REGION is obsolete and only maintained for backwards
compatibility. KVM_SET_USER_MEMORY_REGION should be used instead.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: A question about KVM_SET_MEMORY_REGION ioctl
[not found] ` <1195139900.17876.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
@ 2007-11-15 15:35 ` Zhang, Xiantao
0 siblings, 0 replies; 4+ messages in thread
From: Zhang, Xiantao @ 2007-11-15 15:35 UTC (permalink / raw)
To: Izik Eidus
Cc: carsteno-tA70FqPdS9bQT0dZR+AlfA,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Hollis Blanchard,
Avi Kivity
Izik Eidus wrote:
> 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)
Thank you. Izik! But the name of kvm_vm_ioctl_set_memory_region is
confusing. Maybe we should change it to
kvm_vm_ioctl_set_user_memory_region :-)
Xiantao
-------------------------------------------------------------------------
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-11-15 15:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-15 15:21 A question about KVM_SET_MEMORY_REGION ioctl Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A0466-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-15 15:18 ` Izik Eidus
[not found] ` <1195139900.17876.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-11-15 15:35 ` Zhang, Xiantao
2007-11-15 15:31 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox