Re: [patch] Renaming kvm_arch in view of upcoming architecture ports

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

Christian Ehrhardt wrote:
> Hi,
> in view of the upcoming architecture ports, this is a little cleanup 
> patch that renames the current "_arch" to "_x86"
> e.g. kvm_arch_ops -> kvm_x86_ops
>
> I discussed with some people about names like kvm_x86_arch_ops or 
> kvm_subarch_ops, ... but at the end we thought that "arch" has a 
> special meaning in linux and so it should be freed for the real 
> architecture ports of kvm that show up slowly on the horizon (look at 
> Tucson).
> I want to invite everyone to comment about what may be a more 
> appropriate name in order to find out what naming scheme the community 
> wants.
>
> I attached the patch to keep the usual form, but actually it is just 
> what comes out executing the following:
>  perl -p -i -e "s/_arch/_x86/g" drivers/kvm/*
>

Seems a sensible name.  I thought of subarch at first, but x86 is more 
explicit.

I'll apply this after the lapic merge.

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


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