On Thu, Dec 20, 2012 at 08:51:32AM +0200, Gleb Natapov wrote: > On Wed, Dec 19, 2012 at 11:26:30PM -0200, Marcelo Tosatti wrote: > > On Mon, Dec 17, 2012 at 01:30:49PM +0800, Yang Zhang wrote: > > > From: Yang Zhang <yang.z.zhang@xxxxxxxxx> > > > > > > Virtual interrupt delivery avoids KVM to inject vAPIC interrupts > > > manually, which is fully taken care of by the hardware. This needs > > > some special awareness into existing interrupr injection path: > > > > > > - for pending interrupt, instead of direct injection, we may need > > > update architecture specific indicators before resuming to guest. > > > > > > - A pending interrupt, which is masked by ISR, should be also > > > considered in above update action, since hardware will decide > > > when to inject it at right time. Current has_interrupt and > > > get_interrupt only returns a valid vector from injection p.o.v. > > > > > > Signed-off-by: Kevin Tian <kevin.tian@xxxxxxxxx> > > > Signed-off-by: Yang Zhang <yang.z.zhang@xxxxxxxxx> > > > > > + if (enable_apicv_reg_vid) > > > + kvm_x86_ops->update_cr8_intercept = NULL; > > > + else > > > + kvm_x86_ops->update_apic_irq = NULL; > > > > Loading the module with enable_apicv=0, then enable_apicv=1, > > fails? > It is not changeable after modules is loaded. This is true for all > kvm-intel.ko parameters. Are you sure? Works just fine here. -- 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
