From: Marc Zyngier <maz@kernel.org>
To: "Zengtao (B)" <prime.zeng@hisilicon.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Ganapatrao Kulkarni <gkulkarni@marvell.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"andre.przywara@arm.com" <andre.przywara@arm.com>,
George Cherian <gcherian@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Anil Kumar Reddy H <areddy3@marvell.com>,
"Dave.Martin@arm.com" <Dave.Martin@arm.com>
Subject: Re: [PATCH v2 00/94] KVM: arm64: ARMv8.3/8.4 Nested Virtualization support
Date: Sat, 11 Apr 2020 10:23:56 +0100 [thread overview]
Message-ID: <86r1wus7df.wl-maz@kernel.org> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED342E29B9@dggemm526-mbx.china.huawei.com>
Hi Zengtao,
On Sat, 11 Apr 2020 05:10:05 +0100,
"Zengtao (B)" <prime.zeng@hisilicon.com> wrote:
>
> Hi Marc:
>
> Since it's a very large patch series, I want to test it on my platform
> which don't support nv, and want to make sure if this patch series
> affects the existed virtualization functions or not.
>
> Any suggestion about the test focus?
Not really. Given that the NV patches affect absolutely every
architectural parts of KVM/arm64, everything needs careful
testing. But more than testing, it needs reviewing.
Thanks,
M.
--
Jazz is not dead, it just smells funny.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-04-11 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 7:27 [PATCH v2 00/94] KVM: arm64: ARMv8.3/8.4 Nested Virtualization support George Cherian
2020-04-03 8:02 ` Marc Zyngier
2020-04-11 4:10 ` Zengtao (B)
2020-04-11 9:23 ` Marc Zyngier [this message]
2020-04-16 1:38 ` Zengtao (B)
2020-04-16 18:22 ` Marc Zyngier
2020-04-17 15:06 ` Marc Zyngier
2020-04-18 2:49 ` Zengtao (B)
2020-04-20 14:03 ` Marc Zyngier
2020-04-21 2:22 ` Zengtao (B)
2020-04-17 15:11 ` Alexandru Elisei
-- strict thread matches above, loose matches on Subject: below --
2020-04-03 9:36 George Cherian
2020-04-03 9:49 ` Marc Zyngier
2020-02-11 17:48 Marc Zyngier
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=86r1wus7df.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=andre.przywara@arm.com \
--cc=areddy3@marvell.com \
--cc=gcherian@marvell.com \
--cc=gkulkarni@marvell.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=prime.zeng@hisilicon.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).