Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 4 Sep 2019 09:44:18 -0700
From:   Sean Christopherson <sean.j.christopherson@intel.com>
To:     Alexander Graf <graf@amazon.com>
Cc:     kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org,
        "H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
        Ingo Molnar <mingo@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Joerg Roedel <joro@8bytes.org>,
        Jim Mattson <jmattson@google.com>,
        Wanpeng Li <wanpengli@tencent.com>,
        Vitaly Kuznetsov <vkuznets@redhat.com>,
        Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Liran Alon <liran.alon@oracle.com>
Subject: Re: [PATCH v2 1/2] KVM: VMX: Disable posted interrupts for odd IRQs
Message-ID: <20190904164418.GD24079@linux.intel.com>
References: <20190904133511.17540-1-graf@amazon.com>
 <20190904133511.17540-2-graf@amazon.com>
 <20190904144045.GA24079@linux.intel.com>
 <fcaefade-16c1-6480-aeab-413bcd16dc52@amazon.com>
 <20190904155125.GC24079@linux.intel.com>
 <3f15f8d5-6129-e202-f56e-a5809c41782c@amazon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3f15f8d5-6129-e202-f56e-a5809c41782c@amazon.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Sep 04, 2019 at 05:58:08PM +0200, Alexander Graf wrote:
> 
> On 04.09.19 17:51, Sean Christopherson wrote:
> >On Wed, Sep 04, 2019 at 05:36:39PM +0200, Alexander Graf wrote:
> >>
> >>-	if (!kvm_intr_is_single_vcpu(kvm, &irq, &vcpu)) {
> >>+	if (!kvm_intr_is_single_vcpu(kvm, &irq, &vcpu) ||
> >>+	    !kvm_irq_is_generic(&irq)) {
> >
> >I've never heard/seen the term generic used to describe x86 interrupts.
> >Maybe kvm_irq_is_intr() or kvm_irq_is_vectored_intr()?
> 
> I was trying to come up with any name that describes "interrupt that we can
> post". If "intr" is that, I'll be happy to take it. Vectored_intr sounds
> even worse IMHO :).

kvm_irq_is_intr() is fine by me if it's clear to everyone else.
Alternatively, we could be more literal, e.g. kvm_irq_is_postable().

> 
> >
> >>  		pr_debug("SVM: %s: use legacy intr remap mode for irq %u\n",
> >>  			 __func__, irq.vector);
> >>  		return -1;
> >>@@ -5314,6 +5315,7 @@ static int svm_update_pi_irte(struct kvm *kvm,
> >>unsigned int host_irq,
> >>  		 * 1. When cannot target interrupt to a specific vcpu.
> >>  		 * 2. Unsetting posted interrupt.
> >>  		 * 3. APIC virtialization is disabled for the vcpu.
> >>+		 * 4. IRQ has extended delivery mode (SMI, INIT, etc)
> >
> >Similarly, 'extended delivery mode' isn't really a thing, it's simply the
> >delivery mode.
> 
> s/extended/incompatible/ maybe?

Ya, much better.