On Thu, 24 May 2012, Alex Williamson wrote:
> On Fri, 2012-05-25 at 01:01 +0200, Thomas Gleixner wrote:
> > So the proper fix is that qemu tells the guest that mask bit is
> > supported and catches the mask bit toggling before writing it out to
> > the hardware for those devices which do not support it.
>
> We can't necessarily do that, we have to work with the config space
> we're give. Using the smallest possible MSI capability always works.
> Adding mask bits may not fit in with the existing capabilities of the
> physical device. Thanks,
I see what you mean. A random device driver of a random guest OS might
rely on that information. Unlikely, but ....
So we need some logic to circumvent the masked/unmasked logic in case
that property is not set, right ?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
