LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jagannathan Raman <jag.raman@oracle.com>
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()
Date: Thu, 3 May 2018 14:23:46 +0200 [thread overview]
Message-ID: <20180503122346.nl3dovkyb3py3zpc@8bytes.org> (raw)
In-Reply-To: <1520375981-4958-1-git-send-email-jag.raman@oracle.com>
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 <jag.raman@oracle.com>
Applie, thanks.
prev parent reply other threads:[~2018-05-03 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 22:39 Jagannathan Raman
2018-04-04 18:06 ` Jag Raman
2018-04-20 2:17 ` Jag Raman
2018-05-03 12:23 ` Joerg Roedel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180503122346.nl3dovkyb3py3zpc@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jag.raman@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--subject='Re: [PATCH] iommu/vt-d: fix usage of force parameter in intel_ir_reconfigure_irte()' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).