From: Xiang Zheng <zhengxiang9@huawei.com>
To: <linux-arm-kernel@lists.infradead.org>, <kvmarm@lists.cs.columbia.edu>
Cc: jean-philippe@linaro.org, maz@kernel.org,
wangzhou1@hisilicon.com, prime.zeng@hisilicon.com,
Will Deacon <will@kernel.org>
Subject: [RFC] Use SMMU HTTU for DMA dirty page tracking
Date: Tue, 19 May 2020 17:42:55 +0800 [thread overview]
Message-ID: <b926ec0b-fe87-0792-c41d-acad56c656a4@huawei.com> (raw)
Hi all,
Is there any plan for enabling SMMU HTTU?
I have seen the patch locates in the SVA series patch, which adds
support for HTTU:
https://www.spinics.net/lists/arm-kernel/msg798694.html
HTTU reduces the number of access faults on SMMU fault queue
(permission faults also benifit from it).
Besides reducing the faults, HTTU also helps to track dirty pages for
device DMA. Is it feasible to utilize HTTU to get dirty pages on device
DMA during VFIO live migration?
If SMMU can track dirty pages, devices are not required to implement
additional dirty pages tracking to support VFIO live migration.
--
Thanks,
Xiang
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2020-05-19 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 9:42 Xiang Zheng [this message]
2020-05-22 17:14 ` [RFC] Use SMMU HTTU for DMA dirty page tracking Jean-Philippe Brucker
2020-05-25 11:34 ` Xiang Zheng
2020-05-27 3:27 ` Tian, Kevin
2020-05-27 6:45 ` Xiang Zheng
2020-05-27 8:40 ` Tian, Kevin
2020-05-27 9:14 ` Jean-Philippe Brucker
2021-02-05 3:30 ` Keqian Zhu
2021-02-05 5:21 ` Tian, Kevin
2020-05-27 6:46 ` Zengtao (B)
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=b926ec0b-fe87-0792-c41d-acad56c656a4@huawei.com \
--to=zhengxiang9@huawei.com \
--cc=jean-philippe@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=wangzhou1@hisilicon.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).