From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix interrupt remapping for aliased devices
Date: Mon, 12 May 2014 21:05:12 +0200 [thread overview]
Message-ID: <20140512190511.GB10562@8bytes.org> (raw)
In-Reply-To: <20140422160802.11173.29725.stgit@bling.home>
On Tue, Apr 22, 2014 at 10:08:40AM -0600, Alex Williamson wrote:
> An apparent cut and paste error prevents the correct flags from being
> set on the alias device resulting in MSI on conventional PCI devices
> failing to work. This also produces error events from the IOMMU like:
>
> AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.4 address=0x000000fdf8000000 flags=0x0a00]
>
> Where 14.4 is a PCIe-to-PCI bridge with a device behind it trying to
> use MSI interrupts.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Cc: stable@vger.kernel.org
Applied, thanks Alex.
prev parent reply other threads:[~2014-05-12 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 16:08 [PATCH] iommu/amd: Fix interrupt remapping for aliased devices Alex Williamson
2014-05-12 19:05 ` 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=20140512190511.GB10562@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox