From: Keqian Zhu <zhukeqian1@huawei.com>
To: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <kvm@vger.kernel.org>,
<kvmarm@lists.cs.columbia.edu>, Will Deacon <will@kernel.org>,
Marc Zyngier <maz@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
<wanghaibin.wang@huawei.com>, <jiangkunkun@huawei.com>,
<yuzenghui@huawei.com>, <lushenming@huawei.com>
Subject: Re: [RFC PATCH v2 0/2] kvm/arm64: Try stage2 block mapping for host device MMIO
Date: Wed, 31 Mar 2021 17:13:19 +0800 [thread overview]
Message-ID: <1870563d-4da8-60d6-22e4-242ac820f5ba@huawei.com> (raw)
In-Reply-To: <20210316134338.18052-1-zhukeqian1@huawei.com>
Kind ping...
On 2021/3/16 21:43, Keqian Zhu wrote:
> Hi all,
>
> We have two pathes to build stage2 mapping for MMIO regions.
>
> Create time's path and stage2 fault path.
>
> Patch#1 removes the creation time's mapping of MMIO regions
> Patch#2 tries stage2 block mapping for host device MMIO at fault path
>
> Thanks,
> Keqian
>
> Keqian Zhu (2):
> kvm/arm64: Remove the creation time's mapping of MMIO regions
> kvm/arm64: Try stage2 block mapping for host device MMIO
>
> arch/arm64/kvm/mmu.c | 80 +++++++++++++++++++++++---------------------
> 1 file changed, 41 insertions(+), 39 deletions(-)
>
prev parent reply other threads:[~2021-03-31 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 13:43 [RFC PATCH v2 0/2] kvm/arm64: Try stage2 block mapping for host device MMIO Keqian Zhu
2021-03-16 13:43 ` [RFC PATCH v2 1/2] kvm/arm64: Remove the creation time's mapping of MMIO regions Keqian Zhu
2021-03-16 13:43 ` [RFC PATCH v2 2/2] kvm/arm64: Try stage2 block mapping for host device MMIO Keqian Zhu
2021-04-07 13:18 ` Marc Zyngier
2021-04-08 7:28 ` Keqian Zhu
2021-04-14 6:58 ` Keqian Zhu
2021-04-14 2:48 ` Keqian Zhu
2021-03-31 9:13 ` Keqian Zhu [this message]
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=1870563d-4da8-60d6-22e4-242ac820f5ba@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jiangkunkun@huawei.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lushenming@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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).