On 07/07/2015 17:22, Alex Williamson wrote: >> > -#define __KVM_HAVE_ARCH_NONCOHERENT_DMA >> > +#define __KVM_HAVE_ARCH_VFIO_HOOKS > Do we really want to tie these two things together under something > that's not strictly a "vfio" option? Legacy assignment also makes use > of these, as shown in this patch, but even if we consider that temporary > until legacy assignment is removed, I can imagine platforms that might > care about one but not the other. I don't really see the harm in using > a separate #define, perhaps __KVM_HAVE_ARCH_ASSIGNED_DEVICE. Thanks, Sure, that's okay. Paolo -- 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
