Received: by 10.192.165.148 with SMTP id m20csp1781663imm; Thu, 3 May 2018 05:26:32 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpnu78j/gVS6HLtWEe2wEDgpjunMbBbTgv30uxsuEg+q8EeBocqFaN75MvVOrQmvWnjEmvb X-Received: by 2002:a63:66c3:: with SMTP id a186-v6mr8229464pgc.408.1525350392163; Thu, 03 May 2018 05:26:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525350392; cv=none; d=google.com; s=arc-20160816; b=tltNQSVsav9yFYv1AjGaYYAxQhfhTEvyO+mmlx9n+iGJswblac1YDze3FOsdEoXcds Joez81lfr0Tw8vGB0L+PhJaB3k9uIIJgrpEC2ljAOSBlmcUKvc8WYyqoRhUxU/eyceLR wOUXxziAxK/3JJKwggRSizEioXmqBTztL+VfHmU5S2n2UwNHuOmHT3TTgfiGRTKjTY0f xdcnpEW19VlpgdB9XUz03ax163yQsWFX9/XDF21RjgW5Q/F/lNv9SfcEKW/2Zy5jzVbz nr5iezFb36FJyolTsl6iLhsXnunT1q3YpHOerZ2+zsA+Uniu8p3Ugz6z0jetfCfZFNo1 gnqg== 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:dkim-signature:arc-authentication-results; bh=5IVsdqvzO5iPqKfjjFCFmdqj34BVIRbN9f9vUAAI/YE=; b=q3ISYzaehFs+yDHedMaZUGN/YYlIxMhE6Btw0UOgfXQbVnuGyz/KWRWIYGs3BrDwdo DlJTyoiBRdJdy0mfsNoKe20LiXhs6xlsYE+aXeHpfTZgAkN3H3BEXQ1z9W1e/0Pb84L8 TGWL7mVFd+6jVbUz1qgiV0NUIhKvgv+PINXTkkCQ4XHTzVDmdg8vi1mX5KMwsof1RHd9 NZYKYyXyJSlXywKUWucbnDzPwWxZTLcCgAnqvLxWHuZzyBoP34rRDKXAYhZapcnKzbw0 f3j82x/jjzqbL5jCqhY8ydR3+qd1SB5+fOD8rii9jJ7VVPkxgCqqPt1UXTECUssPKoKl FwPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@8bytes.org header.s=mail-1 header.b=jLR0u++k; 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=8bytes.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a21si13068650pfo.31.2018.05.03.05.26.17; Thu, 03 May 2018 05:26:32 -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; dkim=fail (test mode) header.i=@8bytes.org header.s=mail-1 header.b=jLR0u++k; 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=8bytes.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752224AbeECMYE (ORCPT + 99 others); Thu, 3 May 2018 08:24:04 -0400 Received: from 8bytes.org ([81.169.241.247]:53960 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752116AbeECMXt (ORCPT ); Thu, 3 May 2018 08:23:49 -0400 Received: by theia.8bytes.org (Postfix, from userid 1000) id 9C527188; Thu, 3 May 2018 14:23:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=8bytes.org; s=mail-1; t=1525350227; bh=X+rlpe61xCMkfB4dRJ7KNMCS/aKgdu852OEEha0KLMc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jLR0u++kc7OqslQFF59JCfyQ2r7yiVphDG1KJQpFOIr0PXe8Hju96ev8dSvSR86va z4q+ZntjxTKQYGQnqa43exo5U3m7ffvEsYc6S6KlgPQToUOkgkIrKqKltFS/I7hnzz d4CJcbxWu+BN3VxDCO3qv5oCJL0Ip7q59ZSOQrmo2YLDTm6azYapXJ1MUpUoWGBadw 0NSj52gQRJ8KV6dyCd08VU3HRf7sAq79I8H3KPbSv3VfIHWd2nDsBhfLo+UpoXPfvw TXF9E787jW/f3+7AkHJKZkyeJHrATcCrkwY0GBaSPuMe/RpQlbwObuv0oN0ZEQ7d+9 qL05NFGPq2rGQ== Date: Thu, 3 May 2018 14:23:46 +0200 From: Joerg Roedel To: Jagannathan Raman Cc: tglx@linutronix.de, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] iommu/vt-d: fix usage of force parameter in intel_ir_reconfigure_irte() Message-ID: <20180503122346.nl3dovkyb3py3zpc@8bytes.org> References: <1520375981-4958-1-git-send-email-jag.raman@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520375981-4958-1-git-send-email-jag.raman@oracle.com> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 06, 2018 at 05:39:41PM -0500, Jagannathan Raman wrote: > It was noticed that the IRTE configured for guest OS kernel > was over-written while the guest was running. As a result, > vt-d Posted Interrupts configured for the guest are not being > delivered directly, and instead bounces off the host. Every > interrupt delivery takes a VM Exit. > > It was noticed that the following stack is doing the over-write: > [ 147.463177] modify_irte+0x171/0x1f0 > [ 147.463405] intel_ir_set_affinity+0x5c/0x80 > [ 147.463641] msi_domain_set_affinity+0x32/0x90 > [ 147.463881] irq_do_set_affinity+0x37/0xd0 > [ 147.464125] irq_set_affinity_locked+0x9d/0xb0 > [ 147.464374] __irq_set_affinity+0x42/0x70 > [ 147.464627] write_irq_affinity.isra.5+0xe1/0x110 > [ 147.464895] proc_reg_write+0x38/0x70 > [ 147.465150] __vfs_write+0x36/0x180 > [ 147.465408] ? handle_mm_fault+0xdf/0x200 > [ 147.465671] ? _cond_resched+0x15/0x30 > [ 147.465936] vfs_write+0xad/0x1a0 > [ 147.466204] SyS_write+0x52/0xc0 > [ 147.466472] do_syscall_64+0x74/0x1a0 > [ 147.466744] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 > > reversing the sense of force check in intel_ir_reconfigure_irte() > restores proper posted interrupt functionality > > Signed-off-by: Jagannathan Raman Applie, thanks.