On 01/17/2010 02:50 PM, Gleb Natapov wrote:
I prefer putting this in x86.c (maybe later split into hyperv.c).
This implements part of apic behaviour. It uses internal lapic functions
like apic_reg_read()/apic_reg_write(). Why move it from lapic.c?
The new functions implement hyper-v behaviour. Why scatter them all around?
Each hyper-v extension is pretty much independent one from another, so
why not group things by functionality instead. All apic related code in
lapic.c.
Maybe apic_reg_{read,write} need to be exported.
This is really internal API. It doesn't even check if apic is created.
Okay. We can rethink it later when the code grows some more.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
