On 08/05/2012 11:08 AM, Pekka Enberg wrote: > On 08/04/2012 01:02 PM, Pekka Enberg wrote: >>> No, it's not running 3.5. We need to support older *host* kernels, >>> though. > > On Sun, Aug 5, 2012 at 10:02 AM, Sasha Levin <levinsasha928@xxxxxxxxx> wrote: >> Do we? Don't we need to support just the kernel that the tool was >> built with? > > We only do that for *guest kernels* if we have to but we've always been > compatible with older host kernels. > > Isn't there a capability flag that KVM sets if KVM_SIGNAL_MSI is > supported? Just store that in 'struct kvm" and switch between > virtio_pci__signal_msi() and kvm__irq_trigger() depending on wheter the > flag is set. There is, but we've broken backwards compatibility for guests several times before as well - which is why I assumed thats fine. -- 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
