Re: [PATCH] Add the arg "module" for kvm_arch_init

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Zhang, Xiantao wrote:
> Carsten Otte wrote:
>   
>> Zhang, Xiantao wrote:
>>     
>>> No, THIS_MODULE just stands for itself. But for IA64, we need another
>>> module, and it will register some information to kvm module. So, we
>>> have to keep it.
>>>       
>> That answer confuses me. kvm_arch_init() for ia64 will reside in
>> kvm.ko just like kvm_init(), right?
>> So THIS_MODULE will be the same in kvm_arch_init() and kvm_init(). So
>> which module are you giving as argument?
>>     
>
> Sorry for confusing you. In KVM/IA64 architecture, we have a separate
> module called vmm module to handle mmu and cpu virtualization. It is not
> related to kvm_arch, and will be relocated by kvm.ko when it is
> initilized. So, we have to get some information through its
> registeration when it calls kvm_init. Certaninly, this information
> should be transftered to kvm_arch_init, and handled by ia64-specific
> code. Is it clear now?
>   

Can it not just call an ia64 specific function?


Is it actually required to be a kernel module? (is it linked with the 
rest of the kernel?)  If not, maybe it can be a .o file instead of a 
.ko, and loaded via the request_firmware() mechanism.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/