Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp114146ybe; Thu, 5 Sep 2019 18:31:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqwJaEmd6ATw9Tbp2ALlqB6SgEgPBS8ysLXECV1QkTj886YWeDvAHRtUT3qnpj0MaBSXzbGP X-Received: by 2002:a17:902:ba16:: with SMTP id j22mr6224138pls.253.1567733471191; Thu, 05 Sep 2019 18:31:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567733471; cv=none; d=google.com; s=arc-20160816; b=yTpgE8c5VldDnqu+0CFUYkLejo3KZU7MINwafjaihgCTAz93PrBIGa/o5cekGCSezF kx78EqhwXsT1b8ZFfPs591QP7Pad6RPMAgkXmJQDMC3IbbzpKz9GFOL7ZvzCaMg6HUWU 8pmZLeZfKDmQV8p0mbVYNpwjr2zx6g2Gk6N/7C/87yoQevlI2Tf2w4SWyWEABa7VNz+5 QaOsyRSli0FIgg6ExxoHG4l4NuFQxskSaEEy2+h8+037pCPAu7IJr3y8b2BawuxBeLJc LdRoXbxpI22H5PRTivpe9DSxkYrGzyRWqQfzfcLm1224mi6FY2BsfjMMpcOAsDPInsJH Z0xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=vl5m3Yzpb2HRr1xUrqaUw6xQGgIvDo68WG0/REukzjc=; b=HQrHYdVUnu0L6HZjuJWnPhlVe6q/LwUbiytHpkvbuo/oZTzbEocq2PJsPgCep4jhW2 eV4RuxGNnANVwEGLiaWwqHyDjjl71BIY/yqxe6YQbCd92S4XW6vr9+Q4CNBlC2vk6fHp r/YMJLlOYsKkU9+OvngpcDoyBAdlmzT08blobPV2+TZRlPWY2IB+s+Vfb+c66vttzlCu pOpZNwgD4d/MwNVnrRp1pS4Etwxn4Oy9S+SI6SMBEe8t6DRmBHAxsHbnqjwhV11Nzfjc g6iwePdsY1g51zskFC+vTxxWX9LVvHT9SDzc0N7vwMVAVNGcLlbzO4rCsS3RcKYHPbDt S/zQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f3si3432783plo.166.2019.09.05.18.30.54; Thu, 05 Sep 2019 18:31:11 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390974AbfIERdM (ORCPT + 99 others); Thu, 5 Sep 2019 13:33:12 -0400 Received: from mga03.intel.com ([134.134.136.65]:17592 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726600AbfIERdM (ORCPT ); Thu, 5 Sep 2019 13:33:12 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Sep 2019 10:33:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,470,1559545200"; d="scan'208";a="383936241" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.41]) by fmsmga006.fm.intel.com with ESMTP; 05 Sep 2019 10:33:10 -0700 Date: Thu, 5 Sep 2019 10:33:10 -0700 From: Sean Christopherson To: Alexander Graf Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, "H. Peter Anvin" , Borislav Petkov , Ingo Molnar , Thomas Gleixner , Joerg Roedel , Jim Mattson , Wanpeng Li , Vitaly Kuznetsov , Radim =?utf-8?B?S3LEjW3DocWZ?= , Paolo Bonzini , Liran Alon Subject: Re: [PATCH v3] KVM: x86: Disable posted interrupts for odd IRQs Message-ID: <20190905173310.GA16071@linux.intel.com> References: <20190905125818.22395-1-graf@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190905125818.22395-1-graf@amazon.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 05, 2019 at 02:58:18PM +0200, Alexander Graf wrote: > We can easily route hardware interrupts directly into VM context when > they target the "Fixed" or "LowPriority" delivery modes. > > However, on modes such as "SMI" or "Init", we need to go via KVM code > to actually put the vCPU into a different mode of operation, so we can > not post the interrupt > > Add code in the VMX and SVM PI logic to explicitly refuse to establish > posted mappings for advanced IRQ deliver modes. This reflects the logic > in __apic_accept_irq() which also only ever passes Fixed and LowPriority > interrupts as posted interrupts into the guest. > > This fixes a bug I have with code which configures real hardware to > inject virtual SMIs into my guest. > > Signed-off-by: Alexander Graf > > --- Reviewed-by: Sean Christopherson