From: Chris Wilson <chris@chris-wilson.co.uk>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Andi Shyti <andi.shyti@intel.com>, Lyude Paul <lyude@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
feng.tang@intel.com, zhengjun.xing@intel.com,
guobing.chen@intel.com, ming.a.chen@intel.com,
frank.du@intel.com, Shuhua.Fan@intel.com, wangyang.guo@intel.com,
Wenhuan.Huang@intel.com, jessica.ji@intel.com,
shan.kang@intel.com, guangli.li@intel.com, tiejun.li@intel.com,
yu.ma@intel.com, dapeng1.mi@intel.com, jiebin.sun@intel.com,
gengxin.xie@intel.com, fan.zhao@intel.com
Subject: Re: [drm/i915/gt] 98479ada42: phoronix-test-suite.supertuxkart.1024x768.Windowed.Basic.1.OldMine.frames_per_second -36.0% regression
Date: Fri, 02 Oct 2020 09:43:25 +0100 [thread overview]
Message-ID: <160162820546.4780.2561710802505007406@build.alporthouse.com> (raw)
In-Reply-To: <20201002082740.GI393@shao2-debian>
Quoting kernel test robot (2020-10-02 09:27:40)
> Greeting,
>
> FYI, we noticed a -36.0% regression of phoronix-test-suite.supertuxkart.1024x768.Windowed.Basic.1.OldMine.frames_per_second due to commit:
Where's the power consumption graph? You have a benchmark that although
is running faster than the display is failing to keep the GPU busy. That
alone says there is a latency issue along the GL paths. Is papering over
an issue in command submission worth the power cost?
-Chris
prev parent reply other threads:[~2020-10-02 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 8:27 [drm/i915/gt] 98479ada42: phoronix-test-suite.supertuxkart.1024x768.Windowed.Basic.1.OldMine.frames_per_second -36.0% regression kernel test robot
2020-10-02 8:43 ` Chris Wilson [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=160162820546.4780.2561710802505007406@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=Shuhua.Fan@intel.com \
--cc=Wenhuan.Huang@intel.com \
--cc=andi.shyti@intel.com \
--cc=dapeng1.mi@intel.com \
--cc=fan.zhao@intel.com \
--cc=feng.tang@intel.com \
--cc=frank.du@intel.com \
--cc=gengxin.xie@intel.com \
--cc=guangli.li@intel.com \
--cc=guobing.chen@intel.com \
--cc=jessica.ji@intel.com \
--cc=jiebin.sun@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=lyude@redhat.com \
--cc=ming.a.chen@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=rong.a.chen@intel.com \
--cc=shan.kang@intel.com \
--cc=tiejun.li@intel.com \
--cc=wangyang.guo@intel.com \
--cc=ying.huang@intel.com \
--cc=yu.ma@intel.com \
--cc=zhengjun.xing@intel.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).