From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: aik@ozlabs.ru, paulus@au1.ibm.com, benh@au1.ibm.com,
Wei Yang <weiyang@linux.vnet.ibm.com>
Subject: [PATCH 0/2] powerpc/iommu: check dev->iommu_group before remove it
Date: Fri, 16 Aug 2013 18:08:05 +0800 [thread overview]
Message-ID: <1376647687-20550-1-git-send-email-weiyang@linux.vnet.ibm.com> (raw)
Had a talk with Alexey, who suggest me to send this for comments.
On powernv platform, the P7IOC provide limited range of DMA space. For
example, there are only 8 DMA segments on each PHB. When there are more
than 8 PEs, some of PE's tce32_table is not initialized.
In the normal case, 8 PE is enough. If VF is enabled, 8 is not enough. This
lead to some pci_dev's iommu_table_base is NULL. Which results this device
couldn't be added to any iommu_group, and finally dev->iommu_group is left NULL.
When this VF is removed from the system, this will case kernel crash.
These two patches add the check to guard the kernel. Comments are welcome for
which place is better.
One more comment from Alexey is where we allow these non-DMA capable device
exist in the system. Maybe we should not allow to create a pci_dev for those
who can't get proper DMA space. Your comments are welcome :-)
Thanks in advance.
Wei Yang (2):
iommu: Don't remove device when no iommu_group associated
powerpc/iommu: check dev->iommu_group before remove a device from
iommu_group
arch/powerpc/kernel/iommu.c | 3 ++-
drivers/iommu/iommu.c | 3 +++
2 files changed, 5 insertions(+), 1 deletions(-)
--
1.7.5.4
next reply other threads:[~2013-08-16 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 10:08 Wei Yang [this message]
2013-08-16 10:08 ` [PATCH 1/2] iommu: Don't remove device when no iommu_group associated Wei Yang
2013-08-16 10:08 ` [PATCH 2/2] powerpc/iommu: check dev->iommu_group before remove a device from iommu_group Wei Yang
2013-08-16 10:15 ` Alexey Kardashevskiy
2013-08-19 1:29 ` Wei Yang
2013-08-19 1:39 ` Alexey Kardashevskiy
2013-08-19 1:55 ` Wei Yang
2013-08-22 7:23 ` Alexey Kardashevskiy
2013-08-22 7:52 ` Wei Yang
2013-08-22 15:28 ` Alex Williamson
2013-08-22 15:41 ` Wei Yang
2013-08-22 16:17 ` Alex Williamson
2013-08-23 1:30 ` Wei Yang
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=1376647687-20550-1-git-send-email-weiyang@linux.vnet.ibm.com \
--to=weiyang@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=benh@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@au1.ibm.com \
/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).