Avi Kivity wrote: > Zhang, Xiantao wrote: >> But if users don't configure it @ building kernel, they can't >> exercise kvm unless re-configure and re-build the host kernel. >> Generally, we should allow users to build kvm in the form of >> modules, and insert to host kernels without other dependcies. BTW, >> we often meet such fails and have to do rebuild. :( > > > If users don't configure networking, they can't compile any drivers. > > Sorry, that's how the kernel works. btw, on x86 we manage to run even > without preempt notifiers, but a lot of pain is involved. Yes, we have to do a lot of work to make it work. > In practice, I don't expect a problem. Most users get their kernels > from a distribution. You should talk to ia64 distribution vendors to > make sure they enable kvm in their ia64 2.6.26+ kernels. Agree. Could we change default configration to make preempt_notifier configured if no more overhead introduced ? I noticed kvm/s390 has did in this way. > error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
