From: chenfeng <puck.chen@hisilicon.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <haojian.zhuang@linaro.org>,
<devicetree@vger.kernel.org>, <xuwei5@hisilicon.com>,
<xuyiping@hisilicon.com>, <w.f@huawei.com>,
<kong.kongxinwei@hisilicon.com>, <z.liuxinliang@hisilicon.com>,
<yudongbin@hisilicon.com>, <weidong2@hisilicon.com>,
<saberlily.xia@hisilicon.com>, <linuxarm@huawei.com>,
<dan.zhao@hisilicon.com>, <peter.panshilin@hisilicon.com>,
<qijiwen@hisilicon.com>
Subject: Re: [PATCH 2/3] iommu/hisilicon: Add hi6220 iommu driver
Date: Mon, 19 Oct 2015 09:49:43 +0800 [thread overview]
Message-ID: <56244C37.9030407@hisilicon.com> (raw)
In-Reply-To: <20151014121843.GN27420@8bytes.org>
On 2015/10/14 20:18, Joerg Roedel wrote:
> On Thu, Oct 08, 2015 at 03:45:47PM +0800, Chen Feng wrote:
>> +static int hi6220_smmu_attach_dev(struct iommu_domain *domain,
>> + struct device *dev)
>> +{
>> + struct hi6220_domain *m_domain = to_hi6220_domain(domain);
>> +
>> + smmu_domain_prepare(m_domain);
>> + dev->archdata.iommu = &m_domain->smmu_dev->iova_allocator;
>> +
>> + return 0;
>> +}
>
> What happens when you attach devices behind different smmus to one
> domain? Will that overwrite the smmu_dev pointer in the domain?
>
Since the smmu master use the same pagetable, the master can use the iova_allocator
in smmu driver to allocate iova address.
In this way, the different master can get the different io address.
>> +static size_t hi6220_smmu_unmap(struct iommu_domain *domain, unsigned long iova,
>> + size_t size)
>> +{
>> + struct hi6220_domain *m_domain = to_hi6220_domain(domain);
>> + size_t page_size = m_domain->smmu_dev->page_size;
>> + struct hi6220_smmu *smmu_dev = m_domain->smmu_dev;
>> + int *page_table = (unsigned int *)smmu_dev->pgtable_virt;
>> +
>> + if (size != page_size) {
>> + pr_err("unmap size error, only support %zd\n", page_size);
>> + return 0;
>> + }
>> +
>> + __clear_smmu_pte(page_table + IOVA_PFN(iova));
>> +
>> + return page_size;
>> +}
>
> Don't you need a call to __invalid_smmu_tlb here too?
Thanks, I will fix this next version.
>
>
>
> Joerg
>
>
> .
>
next prev parent reply other threads:[~2015-10-19 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 7:45 [PATCH 1/3] docs: dts: Documentation for smmu in hi6220 SoC Chen Feng
2015-10-08 7:45 ` [PATCH 2/3] iommu/hisilicon: Add hi6220 iommu driver Chen Feng
2015-10-14 12:18 ` Joerg Roedel
2015-10-19 1:49 ` chenfeng [this message]
2015-10-08 7:45 ` [PATCH 3/3] arm64: dts: Add dts node for hi6220 iommu Chen Feng
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=56244C37.9030407@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=dan.zhao@hisilicon.com \
--cc=devicetree@vger.kernel.org \
--cc=haojian.zhuang@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=pawel.moll@arm.com \
--cc=peter.panshilin@hisilicon.com \
--cc=qijiwen@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=saberlily.xia@hisilicon.com \
--cc=w.f@huawei.com \
--cc=weidong2@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=xuyiping@hisilicon.com \
--cc=yudongbin@hisilicon.com \
--cc=z.liuxinliang@hisilicon.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
Powered by JetHome