Hi Drew, Zenghui,
On 4/2/2020 7:52 PM, Zenghui Yu wrote:
Hi Drew, Jingyi,
On 2020/4/1 20:24, Andrew Jones wrote:
On Wed, Apr 01, 2020 at 06:08:10PM +0800, Jingyi Wang wrote:
With the development of arm gic architecture, we think it will be useful
to add some simple performance test in kut to measure the cost of
interrupts. X86 arch has implemented similar test.
Jingyi Wang (2):
arm/arm64: gic: Add IPI latency test
arm/arm64: Add vtimer latency test
arm/gic.c | 27 +++++++++++++++++++++++++++
arm/timer.c | 11 +++++++++++
2 files changed, 38 insertions(+)
--
2.19.1
Hi Jingyi,
We already have an IPI latency test in arm/micro-bench.c I'd prefer that
one be used, if possible, rather than conflating the gic functional tests
with latency tests. Can you take a look at it and see if it satisfies
your needs, extending it if necessary?
I think it'd be good to have these interrupt latency measurements in
kvm-unit-tests, and we can take the following interrupt types into
account:
- IPI
As Drew pointed out, we already have one in the micro-bench group.
But what I'm actually interested in is the latency of the new GICv4.1
vSGIs (which will be directly injected through ITS). To measure it,
we should first make KUT be GICv4.1-awareness, see [1] for details.
(This way, we can even have a look at the interrupt latency in HW
level. Is it possible to have this in kvm-unit-tests, Drew?)
- PPI
Like what has been done in patch #2, you can choose the vtimer
interrupt as an example.
- LPI
I think we can easily build a LPI latency test based on Eric's "ITS
tests" series [2], which should be upstreamed soon.
- if you want to add more...
What do you think? I'd like to see a V2 of this series :-).
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0b04758b002bde9434053be2fff8064ac3d9d8bb
[2]
https://lore.kernel.org/kvm/20200320092428.20880-1-eric.auger@xxxxxxxxxx/
Thanks,
Zenghui
.
As Drew mentioned, I am thinking about adding other gic functional tests
in arm/micro-bench.c. Thanks for your suggestion, I think it's of great
help.
Thanks,
Jingyi
