From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH 0/2] Bug fix for VFIO EEH
Date: Tue, 15 Jul 2014 17:00:54 +1000 [thread overview]
Message-ID: <1405407656-3751-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
Those 2 patches are bug fix for VFIO EEH support, which isn't merged yet though
all reviewers gave their ack. So I'm sending this to avoid revert or something
like that.
The problem is that dma_offset/iommu_table_base
are sharing same memory location. When disabling bypass mode, we missed to restore
iommu_table_base. EEH is utilizing that to translate IOMMU group ID to PE. The
patches fix the issue.
Another issue is that we're searching all online PCI devices for translating
IOMMU group ID to PE. That's incorrect since we're uncertain that one speicific
device (except those in current IOMMU group) is running in bypassed mode or
not. So we should have search current IOMMU group.
It should be applied on top of unmerged VFIO EEH support patchset:
http://patchwork.ozlabs.org/patch/357665/
Gavin Shan (2):
powerpc/powernv: Fix IOMMU table for VFIO dev
powerpc/eeh: Fetch IOMMU table in reliable way
arch/powerpc/kernel/eeh.c | 33 ++++++++++++++++++++-----------
arch/powerpc/platforms/powernv/pci-ioda.c | 30 +++++++++++++++++++---------
2 files changed, 43 insertions(+), 20 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-07-15 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 7:00 Gavin Shan [this message]
2014-07-15 7:00 ` [PATCH 1/2] powerpc/powernv: Fix IOMMU table for VFIO dev Gavin Shan
2014-07-15 7:00 ` [PATCH 2/2] powerpc/eeh: Fetch IOMMU table in reliable way Gavin Shan
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=1405407656-3751-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).