From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: A question about KVM_SET_MEMORY_REGION ioctl Date: Thu, 15 Nov 2007 17:31:32 +0200 Message-ID: <473C6654.3030703@qumranet.com> References: <42DFA526FC41B1429CE7279EF83C6BDC9A0466@pdsmsx415.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org, kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Hollis Blanchard To: "Zhang, Xiantao" Return-path: In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC9A0466-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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/