Avi Kivity wrote: > I must say I'm pleasantly surprised by this. I keep thinking of ppc and > ia64 as additional ports, while ignoring the big daddy of virtualization. Thank you very much for the warm welcome :-).
>> Similar to the kvm interface on x86, this interface is >> hardware dependent at this time. Patches apply against 2.6.21, please >> review. > > It's all greek to me. Actually I felt the same about reading much of the kvm kernel code. Both architectures are rather different, and our task will be to identify spots where we can abstract to get code that is common for all architectures and find out where we need architecture dependent code. > The address space and vcpu management are rather different from kvm's, > however your approach is better and we'll want to move kvm in your > direction rather than the other way round (specifically the tight vcpu > <-> task coupling; mmu is more diffcult). We have tried a file based approach for the cpus before too. With regard to the memory, I do not quite understand why regular pageable user space memory does'nt work with vt and svm. We would definetly prefer to keep our virtual machine's memory pageable on s390, therefore I guess we need some arch dependent plug that allocates the memory. This would boil down to a regular anonymous allocation on s390, and to specifically allocated memory on x86. so long, Carsten ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
