From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: RFC/patch portability: split kvm_vm_ioctl v3 Date: Tue, 30 Oct 2007 13:03:58 +0200 Message-ID: <47270F9E.5080007@qumranet.com> References: <1192192452.7630.16.camel@cotte.boeblingen.de.ibm.com><1193327325.8345.9.camel@cotte.boeblingen.de.ibm.com> <1193400099.10970.8.camel@cotte.boeblingen.de.ibm.com> <10EA09EFD8728347A513008B6B0DA77A024CEC4D@pdsmsx411.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0910635768==" Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Carsten Otte , Hollis Blanchard , "Zhang, Xiantao" To: "Dong, Eddie" Return-path: In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A024CEC4D-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@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 --===============0910635768== Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Dong, Eddie wrote: > =20 > > =20 >> -----Original Message----- >> From: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org=20 >> [mailto:kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of=20 >> Carsten Otte >> Sent: 2007=C4=EA10=D4=C226=C8=D5 20:02 >> To: Avi Kivity; Zhang, Xiantao; Hollis Blanchard >> Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >> Subject: Re: [kvm-devel] RFC/patch portability: split kvm_vm_ioctl v3 >> >> This patch splits kvm_vm_ioctl into archtecture independent parts, and >> x86 specific parts which go to kvm_arch_vcpu_ioctl in x86.c.=20 >> The patch has been updated to current git, and it leaves out=20 >> memory slot >> registration work which is currently subject to a detailed discussion. >> >> Common ioctls for all architectures are: >> KVM_CREATE_VCPU, KVM_GET_DIRTY_LOG, KVM_SET_USER_MEMORY_REGION >> >> KVM_SET_USER_MEMORY_REGION implementation is no longer moved to x86.c. >> It seems to me that more fine-grained refinement then just moving the >> code is required here. >> >> x86 specific ioctls are: >> KVM_SET_MEMORY_REGION,=20 >> KVM_GET/SET_NR_MMU_PAGES, KVM_SET_MEMORY_ALIAS, KVM_CREATE_IRQCHIP, >> KVM_CREATE_IRQ_LINE, KVM_GET/SET_IRQCHIP >> KVM_SET_TSS_ADDR >> >> KVM_SET_TSS_ADDR has been added to the list of x86 specifics, as Izik'= s >> commit states it is used for emulating real mode on intel. >> >> =20 > Why KVM_IRQ_LINE is X86b specific? The original idea are based on ACPI = spec which > I assume to be generic though S390 may not take. > > =20 ia64 can probably share much. ppc will probably want KVM_IRQ_LINE with with different parameters. s390, as far as I understand, will not. --=20 Any sufficiently difficult bug is indistinguishable from a feature. --===============0910635768== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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/ --===============0910635768== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kvm-devel mailing list kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/kvm-devel --===============0910635768==--