On Fri, Feb 22, 2019 at 12:28:27PM +0100, Cédric Le Goater wrote: > The user interface exposes a new capability to let QEMU connect the > vCPU to the XIVE KVM device if required. The capability is only > advertised on a PowerNV Hypervisor as support for nested guests > (pseries KVM Hypervisor) is not yet available. If a bisection happened to land on this commit, we would have KVM saying it had the ability to support guests using XIVE natively, but it wouldn't actually work since we don't have all the code that is in the following patches. Thus, in order to avoid breaking bisection, you should either add the capability now but have it always return false until the rest of the code is in place, or else defer the addition of the capability until the end of the patch series. > diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c > index 8c69af10f91d..a38a643a24dd 100644 > --- a/arch/powerpc/kvm/powerpc.c > +++ b/arch/powerpc/kvm/powerpc.c > @@ -570,6 +570,12 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext) > case KVM_CAP_PPC_GET_CPU_CHAR: > r = 1; > break; > +#ifdef CONFIG_KVM_XIVE > + case KVM_CAP_PPC_IRQ_XIVE: > + /* only for PowerNV */ > + r = !!cpu_has_feature(CPU_FTR_HVMODE); Shouldn't this be r = xive_enabled() && !!cpu_has_feature(CPU_FTR_HVMODE) (or alternatively r = xics_on_xive(), though that would be confusing to the reader)? As it stands this would report true on POWER8, unless I'm missing something. Paul.
