Dong, Eddie wrote:
>
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of
>> Carsten Otte
>> Sent: 2007年10月26日 20:02
>> To: Avi Kivity; Zhang, Xiantao; Hollis Blanchard
>> Cc: kvm-devel@lists.sourceforge.net
>> 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.
>> The patch has been updated to current git, and it leaves out
>> 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,
>> 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.
>>
>>
> 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.
>
>
ia64 can probably share much. ppc will probably want KVM_IRQ_LINE with
with different parameters. s390, as far as I understand, will not.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
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
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
