On 08/05/2012 11:08 AM, Pekka Enberg wrote:
>> 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.
On Sun, Aug 5, 2012 at 12:14 PM, Sasha Levin <levinsasha928@xxxxxxxxx> wrote:
> There is, but we've broken backwards compatibility for guests several
> times before as well - which is why I assumed thats fine.
Let me be clear about this: I don't like breaking backwards
compatibility at all. Yes, we have done it in the past for *guest
kernels* for various technical reasons but we've never ever done it on
purpose for host kernels.
We have been more relaxed on backwards compatibility requirements than
QEMU but I think we're reaching a point where it's more painful to break
backwards compatibility than it is to write code to accommodate older
kernels. Especially for something like this which is obviously a new KVM
feature and not required for running Linux.
Pekka
--
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
