From: Marc Zyngier <maz@kernel.org>
To: shawnguo@kernel.org, linux@rasmusvillemoes.dk,
leoyang.li@nxp.com, mark.rutland@arm.com, zhiqiang.hou@nxp.com,
Biwen Li <biwen.li@oss.nxp.com>,
robh+dt@kernel.org, tglx@linutronix.de,
kvmarm@lists.cs.columbia.edu, Will Deacon <will@kernel.org>,
kvm@vger.kernel.org, Eric Auger <eric.auger@redhat.com>,
Christoffer Dall <christoffer.dall@arm.com>,
linux-arm-kernel@lists.infradead.org,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Shenming Lu <lushenming@huawei.com>,
James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
Julien Thierry <julien.thierry.kdev@gmail.com>
Cc: xiaobo.xie@nxp.com, Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
devicetree@vger.kernel.org, Biwen Li <biwen.li@nxp.com>,
jiafei.pan@nxp.com, yuzenghui@huawei.com,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH v2 0/2] KVM: arm64: Optimize the wait for the completion of the VPT analysis
Date: Fri, 11 Dec 2020 15:01:39 +0000 [thread overview]
Message-ID: <160769813659.482133.2716418035359567004.b4-ty@kernel.org> (raw)
In-Reply-To: <20201128141857.983-1-lushenming@huawei.com>
On Sat, 28 Nov 2020 22:18:55 +0800, Shenming Lu wrote:
> Right after a vPE is made resident, the code starts polling the
> GICR_VPENDBASER.Dirty bit until it becomes 0, where the delay_us
> is set to 10. But in our measurement, it takes only hundreds of
> nanoseconds, or 1~2 microseconds, to finish parsing the VPT in most
> cases. What's more, we found that the MMIO delay on GICv4.1 system
> (HiSilicon) is about 10 times higher than that on GICv4.0 system in
> kvm-unit-tests (the specific data is as follows).
>
> [...]
Applied to irq/irqchip-next, thanks!
[1/2] irqchip/gic-v4.1: Reduce the delay time of the poll on the GICR_VPENDBASER.Dirty bit
commit: 0b39498230ae53e6af981141be99f4c7d5144de6
Patch 2 will be routed via the KVM/arm64 tree.
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2020-12-11 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 14:18 Shenming Lu
2020-11-28 14:18 ` [PATCH v2 1/2] irqchip/gic-v4.1: Reduce the delay time of the poll on the GICR_VPENDBASER.Dirty bit Shenming Lu
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] irqchip/gic-v4.1: Reduce the delay when polling GICR_VPENDBASER.Dirty irqchip-bot for Shenming Lu
2020-11-28 14:18 ` [PATCH v2 2/2] KVM: arm64: Delay the execution of the polling on the GICR_VPENDBASER.Dirty bit Shenming Lu
2020-11-30 11:22 ` Marc Zyngier
2020-11-30 12:12 ` Shenming Lu
2020-11-30 12:28 ` Marc Zyngier
2020-12-11 15:01 ` Marc Zyngier [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=160769813659.482133.2716418035359567004.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=biwen.li@nxp.com \
--cc=biwen.li@oss.nxp.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=jiafei.pan@nxp.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lushenming@huawei.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=xiaobo.xie@nxp.com \
--cc=yuzenghui@huawei.com \
--cc=zhiqiang.hou@nxp.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
all inboxes | Powered by JetHome®