Re: [Patch][RFC]Split kvm_vcpu to support new archs.

[Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>]

Zhang, Xiantao wrote:
>>> So, every
>>> architecture can defines its own kvm_arch.h for their arch, and
>>> compile will choose it per ARCH when compile time. But for now, we
>>> can just put it here before another real new arch in.  Then, we can
>>> remove x86.h, since it is not so common for all archs.  :)
>>> BTW, header files should be managed with a uniform method, because
>>> possible archs, such as IA64, maybe need many ones.
>> That's fine with me. But prior to that we'll need to split x86 so that
>> it can be relocated in its arch directory different from the common
>> kvm location. And until we're there, we use x86.h as a place to store
>> x86 specific header content.
> 
> OK, I will change it to x86.h, but we also renamed it to such
> "kvm_arch.h", because kvm.h will includes it. 
Which kvm.h? The one in include/linux or the one in drivers/kvm?

-------------------------------------------------------------------------
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/