From: David Woodhouse <dwmw2@infradead.org>
To: Ashok Raj <ashok.raj@intel.com>, linux-kernel@vger.kernel.org
Cc: Joerg Roedel <joro@8bytes.org>,
Sainath Grandhi <sainath.grandhi@intel.com>,
iommu@lists.linux-foundation.org, stable@vger.kernel.org
Subject: Re: [PATCH] iommu/vt-d: Fix IOMMU lookup for VF's
Date: Sun, 30 Oct 2016 06:10:06 -0600 [thread overview]
Message-ID: <1477829406.4154.2.camel@infradead.org> (raw)
In-Reply-To: <1477089125-18523-1-git-send-email-ashok.raj@intel.com>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Fri, 2016-10-21 at 15:32 -0700, Ashok Raj wrote:
> IOMMU driver must pick the same IOMMU as that of a Physical Function (PF) for
> any of its Virtual Functions (VF). It is not practical to list all the VF's
> in the DMAR scope, as this list could be quite large. Linux also ignores any
> VF's listed in DMAR. See dmar_pci_bus_notifier() for virtfn handling.
>
> Since the driver is looking for the bdf of the VF, it will not find one from
> searching the DRHD listed in BIOS. As a result, the IOMMU driver associates
> the VF's under the INCLUDE_ALL iommu incorrectly.
>
> This patch looks up the IOMMU of the PF when handling VF's.
I've made some cosmetic fixes — adding comments, and tweaking the
commit comment — and applied this to my tree. Thanks.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5760 bytes --]
prev parent reply other threads:[~2016-10-30 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 22:32 [PATCH] iommu/vt-d: Fix IOMMU lookup for VF's Ashok Raj
2016-10-30 12:10 ` David Woodhouse [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=1477829406.4154.2.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=ashok.raj@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sainath.grandhi@intel.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).