From: chenfeng <puck.chen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
xuyiping-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
w.f-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
kong.kongxinwei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
z.liuxinliang-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
yudongbin-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
weidong2-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
saberlily.xia-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
peter.panshilin-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
qijiwen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org
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-zLv9SwRftAIdnm+yROfE0A@public.gmane.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
>
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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:49 UTC|newest]
Thread overview: 10+ 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 ` Chen Feng
2015-10-08 7:45 ` [PATCH 2/3] iommu/hisilicon: Add hi6220 iommu driver Chen Feng
2015-10-08 7:45 ` Chen Feng
[not found] ` <1444290348-66509-2-git-send-email-puck.chen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2015-10-14 12:18 ` Joerg Roedel
2015-10-14 12:18 ` Joerg Roedel
[not found] ` <20151014121843.GN27420-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-10-19 1:49 ` chenfeng [this message]
2015-10-19 1:49 ` chenfeng
2015-10-08 7:45 ` [PATCH 3/3] arm64: dts: Add dts node for hi6220 iommu Chen Feng
2015-10-08 7:45 ` 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-c8/m+/jpzteamjb+lgu22q@public.gmane.org \
--cc=dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=kong.kongxinwei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=peter.panshilin-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=qijiwen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=saberlily.xia-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=w.f-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=weidong2-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=xuyiping-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=yudongbin-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
--cc=z.liuxinliang-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.