Re: [PATCH v2 0/2] KVM: arm64: Optimize the wait for the completion of the VPT analysis

* Re: [PATCH v2 0/2] KVM: arm64: Optimize the wait for the completion of the VPT analysis
       [not found] <20201128141857.983-1-lushenming@huawei.com>
@ 2020-12-11 15:01 ` Marc Zyngier
  0 siblings, 0 replies; only message in thread
From: Marc Zyngier @ 2020-12-11 15:01 UTC (permalink / raw)
  To: shawnguo, linux, leoyang.li, mark.rutland, zhiqiang.hou,
	Biwen Li, robh+dt, tglx, kvmarm, Will Deacon, kvm, Eric Auger,
	Christoffer Dall, linux-arm-kernel, Suzuki K Poulose,
	Shenming Lu, James Morse, Catalin Marinas, linux-kernel,
	Julien Thierry
  Cc: xiaobo.xie, Hou Zhiqiang, devicetree, Biwen Li, jiafei.pan,
	yuzenghui, wanghaibin.wang

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.

^ permalink raw reply	[flat|nested] only message in thread