From: John Garry <john.garry@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>, Will Deacon <will@kernel.org>
Cc: <joro@8bytes.org>, <baolu.lu@linux.intel.com>,
<iommu@lists.linux-foundation.org>, <linuxarm@huawei.com>,
<thierry.reding@gmail.com>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<jonathanh@nvidia.com>, <sakari.ailus@linux.intel.com>,
<bingbu.cao@intel.com>, <tian.shu.qiu@intel.com>,
<mchehab@kernel.org>, <gregkh@linuxfoundation.org>,
<digetx@gmail.com>, <mst@redhat.com>, <jasowang@redhat.com>,
<linux-kernel@vger.kernel.org>, <chenxiang66@hisilicon.com>
Subject: Re: [PATCH v4 5/6] iova: Add iova_len argument to init_iova_domain()
Date: Tue, 21 Sep 2021 09:48:51 +0100 [thread overview]
Message-ID: <4add7fb2-e9de-9c15-1915-6a6e2596941d@huawei.com> (raw)
In-Reply-To: <1d06eda1-9961-d023-f5e7-fe87e768f067@arm.com>
On 02/08/2021 17:16, Robin Murphy wrote:
>>>>
>>>> Also fix up all users to set this value (at 0, meaning use default).
>>> Wrap that in init_iova_domain_defaults() to avoid the mysterious 0?
>>
>> Sure, I can do something like that. I actually did have separate along
>> those lines in v3 before I decided to change it.
>
> Y'know, at this point I'm now starting to seriously wonder whether
> moving the rcaches into iommu_dma_cookie wouldn't make a whole lot of
> things simpler... :/
>
> Does that sound like crazy talk to you, or an idea worth entertaining?
Hi Robin,
JFYI, to try to make inroads into my IOVA issues, I'm going to look to
do this first, if you don't mind. I think that the fq stuff can also be
put into a separate structure also, rather than iova_domain, and that
can also be a member of iommu_dma_cookie.
BTW, with regards to separating the rcache magazine code out, I see
someone already trying to introduce something similar:
https://lore.kernel.org/lkml/CAKW4uUxperg41z8Lu5QYsS-YEGt1anuD1CuiUqXC0ANFqJBosQ@mail.gmail.com/T/#me4cc5de775ad16ab3d6e7ca854b55f274ddcba08
https://lore.kernel.org/lkml/YUkErK1vVZMht4s8@casper.infradead.org/T/#t
Cheers,
John
next prev parent reply other threads:[~2021-09-21 8:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 10:36 [PATCH v4 0/6] iommu: Allow IOVA rcache range be configured John Garry
2021-07-14 10:36 ` [PATCH v4 1/6] iommu: Refactor iommu_group_store_type() John Garry
2021-08-02 14:46 ` Will Deacon
2021-07-14 10:36 ` [PATCH v4 2/6] iova: Allow rcache range upper limit to be flexible John Garry
2021-08-02 15:01 ` Will Deacon
2021-08-02 15:23 ` John Garry
2021-08-02 16:09 ` Robin Murphy
2021-07-14 10:36 ` [PATCH v4 3/6] iommu: Allow iommu_change_dev_def_domain() realloc default domain for same type John Garry
2021-07-14 10:36 ` [PATCH v4 4/6] iommu: Allow max opt DMA len be set for a group via sysfs John Garry
2021-07-14 10:36 ` [PATCH v4 5/6] iova: Add iova_len argument to init_iova_domain() John Garry
2021-08-02 15:06 ` Will Deacon
2021-08-02 16:06 ` John Garry
2021-08-02 16:16 ` Robin Murphy
2021-08-02 16:40 ` John Garry
2021-08-02 17:18 ` John Garry
2021-09-21 8:48 ` John Garry [this message]
2021-07-14 10:36 ` [PATCH v4 6/6] dma-iommu: Pass iova len for IOVA domain init John Garry
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=4add7fb2-e9de-9c15-1915-6a6e2596941d@huawei.com \
--to=john.garry@huawei.com \
--cc=airlied@linux.ie \
--cc=baolu.lu@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=chenxiang66@hisilicon.com \
--cc=daniel@ffwll.ch \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jasowang@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab@kernel.org \
--cc=mst@redhat.com \
--cc=robin.murphy@arm.com \
--cc=sakari.ailus@linux.intel.com \
--cc=thierry.reding@gmail.com \
--cc=tian.shu.qiu@intel.com \
--cc=will@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).