From: John Garry <john.garry@huawei.com>
To: <joro@8bytes.org>, <robin.murphy@arm.com>
Cc: <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <chenxiang66@hisilicon.com>,
<linuxarm@huawei.com>, <xiyou.wangcong@gmail.com>,
<thunder.leizhen@huawei.com>, John Garry <john.garry@huawei.com>
Subject: [PATCH 0/2] iommu/iova: Solve longterm IOVA issue
Date: Fri, 25 Sep 2020 17:51:07 +0800 [thread overview]
Message-ID: <1601027469-221812-1-git-send-email-john.garry@huawei.com> (raw)
This series contains a patch to solve the longterm IOVA issue which
leizhen originally tried to address at [0].
I also included the small optimisation from Cong Wang, which never seems
to be have been accepted [1]. There was some debate of the other patches
in that series, but this one is quite straightforward.
@Cong Wang, Please resend your series if prefer I didn't upstream your
patch.
[0] https://lore.kernel.org/linux-iommu/20190815121104.29140-3-thunder.leizhen@huawei.com/
[1] https://lore.kernel.org/linux-iommu/4b74d40a-22d1-af53-fcb6-5d70183705a8@huawei.com/
Cong Wang (1):
iommu: avoid taking iova_rbtree_lock twice
John Garry (1):
iommu/iova: Flush CPU rcache for when a depot fills
drivers/iommu/iova.c | 33 ++++++++++++++++++++++-----------
1 file changed, 22 insertions(+), 11 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-25 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:51 John Garry [this message]
2020-09-25 9:51 ` [PATCH 1/2] iommu/iova: Flush CPU rcache for when a depot fills John Garry
2020-09-25 11:53 ` Robin Murphy
2020-09-25 14:34 ` John Garry
2020-09-25 16:12 ` John Garry
2020-09-25 9:51 ` [PATCH 2/2] iommu: avoid taking iova_rbtree_lock twice John Garry
2020-09-25 19:26 ` [PATCH 0/2] iommu/iova: Solve longterm IOVA issue Cong Wang
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=1601027469-221812-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=thunder.leizhen@huawei.com \
--cc=xiyou.wangcong@gmail.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).