From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Patch][RFC]Split kvm_vcpu to support new archs. Date: Tue, 16 Oct 2007 12:21:28 +0200 Message-ID: <471490A8.5050502@qumranet.com> References: <42DFA526FC41B1429CE7279EF83C6BDC808C85@pdsmsx415.ccr.corp.intel.com> <471075A4.5030809@qumranet.com> <42DFA526FC41B1429CE7279EF83C6BDC808F90@pdsmsx415.ccr.corp.intel.com> <47132F84.9070002@qumranet.com> <42DFA526FC41B1429CE7279EF83C6BDC809429@pdsmsx415.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: "Zhang, Xiantao" Return-path: In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC809429-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: > >>> About mmu, i am not sure about this. IA64 only need kvm module to >>> allocate and free memory for guests. Most functions related to mmu >>> are useless for IA64. If we put them as common, Maybe we have to >>> define some blank functions. >>> >>> >>> >> I meant the mmu is x86 specific. >> > > Sorry for misunderstanding. Should we move out the code logic related > to mmu from kvm_main.c , and put them as arch-specific code ?:) > > Yes. But from what I looked, there isn't much mmu code in kvm_main.c, only calls to mmu code. >>>> pio is x86 specific >>>> >>>> >>> Why see pio as x86 specific? as I know, most archs have port IO >>> access . >>> >>> >>> >> Which ones? ppc and s390 don't, and I think ia64 doesn't either? >> > > Yes, IA64 hasn't separate IO address space, and do hasn't Port IO access > with directy IO instructions. But for compatibility with Legacy devices, > all IO ports in devices are sparsely mapped into 64M MMIO space, so we > need to translate them inoto port IO for IO device emulation in > virtualization world. Anyway, this is not a big problem, up to you: ) > We can do this translation in userspace, unless there's a device you want to emulate in the kernel that uses pio. -- 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/