From: Marc Zyngier <marc.zyngier@arm.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
"Tangnianyao (ICT)" <tangnianyao@huawei.com>,
Christoffer Dall <christoffer.dall@arm.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"julien.thierry@arm.com" <julien.thierry@arm.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"alex.bennee@linaro.org" <alex.bennee@linaro.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"andre.przywara@arm.com" <andre.przywara@arm.com>,
Zhangshaokun <zhangshaokun@hisilicon.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH] KVM: arm/arm64: Set ICH_HCR_EN in guest anyway when using gicv4
Date: Wed, 13 Mar 2019 16:31:05 +0000 [thread overview]
Message-ID: <09a615e5-9dce-d194-6290-b8897abd5d12@arm.com> (raw)
In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA839311C4F@lhreml524-mbs.china.huawei.com>
On 13/03/2019 15:59, Shameerali Kolothum Thodi wrote:
Hi Shameer,
>> Can you please give the following patch a go? I can't test it, but hopefully
>> you can.
>
> Thanks for your quick response. I just did a quick test on one of our platforms
> with VHE+GICv4 and it seems to fix the performance issue we were seeing
> when GICv4 is enabled.
>
> Test setup:
>
> Host connected to a PC over a 10G port.
> Launch Guest with an assigned vf dev.
> Run iperf from Guest,
>
> 5.0 kernel:
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 1.30 GBytes 1.12 Gbits/sec
>
> +Patch:
>
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 10.9 GBytes 9.39 Gbits/sec
Ah, that looks much better! I'll try to write it properly, as I think
what we have today is slightly bizarre (we write ICH_HCR_EL2 from too
many paths, and I need to remember how the whole thing works).
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2019-03-13 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F348A9E21A573744858FF7E5D32E29D81FEFA462@DGGEMI529-MBX.china.huawei.com>
2019-03-12 15:48 ` Marc Zyngier
2019-03-13 11:59 ` Marc Zyngier
2019-03-13 15:59 ` Shameerali Kolothum Thodi
2019-03-13 16:31 ` Marc Zyngier [this message]
2019-03-14 8:05 ` Tangnianyao (ICT)
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=09a615e5-9dce-d194-6290-b8897abd5d12@arm.com \
--to=marc.zyngier@arm.com \
--cc=alex.bennee@linaro.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=james.morse@arm.com \
--cc=julien.thierry@arm.com \
--cc=keescook@chromium.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suzuki.poulose@arm.com \
--cc=tangnianyao@huawei.com \
--cc=will.deacon@arm.com \
--cc=zhangshaokun@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
all inboxes | Powered by JetHome®