From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] benchmarks/wsim: Simulate and interpret .wsim
Date: Tue, 10 Jul 2018 17:05:18 +0100 [thread overview]
Message-ID: <b957c6d9-0c07-17a8-b965-fe0d1e9f19b4@linux.intel.com> (raw)
In-Reply-To: <153123723883.18500.4422793026340793958@skylake-alporthouse-com>
On 10/07/2018 16:40, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-07-10 16:38:14)
>>
>> On 10/07/2018 14:47, Chris Wilson wrote:
>>> Quoting Tvrtko Ursulin (2018-05-11 09:31:52)
>>>>
>>>> On 11/05/2018 08:11, Chris Wilson wrote:
>>>>> A little tool I've been meaning to write for a while... Convert the
>>>>> .wsim into their dag and find the longest chains and evaluate them on an
>>>>> simulated machine.
>>>>
>>>> Very cool!
>>>
>>> Would you care to ack it in its current form, knowing that we will fix
>>> it whenever we find a corner case interesting enough to study?
>>
>> I think just a little bit more polish is needed. I've just tried it out
>> and polish I can see is:
>>
>> 1. -h / --help with just a brief comment on what the tool does and usage.
>>
>> 2. Lead stats displayed for each cmdline argument with parsed filename.
>>
>> 3. Replace result section names "Single client", "Simulated clients" and
>> item names "total/ideal/packed" with a more descriptive text which would
>> hopefully be somewhat self-explanatory what the numbers represent.
>>
>> 4. Report garbage input (and unknown wsim commands) instead of reporting
>> some numbers for instance for ./sim_wsim README :)
>>
>> 5. #ifdef 0 graphviz ? add --graphviz cmddline option?
>>
>> 6. Oh.. and meson makefiles.. :)
>
> But if it was upstream, you would just contribute those improvements
> yourself.
>
> So you are saying that this is just not useful?
No, just that I think we have to have some minimum standard before we
can make it upstream. If you want I can implement these bits and send a
v3. Then it will just be a matter of finding a third person to review it
since we will both be authors. :)
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] benchmarks/wsim: Simulate and interpret .wsim
Date: Tue, 10 Jul 2018 17:05:18 +0100 [thread overview]
Message-ID: <b957c6d9-0c07-17a8-b965-fe0d1e9f19b4@linux.intel.com> (raw)
In-Reply-To: <153123723883.18500.4422793026340793958@skylake-alporthouse-com>
On 10/07/2018 16:40, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-07-10 16:38:14)
>>
>> On 10/07/2018 14:47, Chris Wilson wrote:
>>> Quoting Tvrtko Ursulin (2018-05-11 09:31:52)
>>>>
>>>> On 11/05/2018 08:11, Chris Wilson wrote:
>>>>> A little tool I've been meaning to write for a while... Convert the
>>>>> .wsim into their dag and find the longest chains and evaluate them on an
>>>>> simulated machine.
>>>>
>>>> Very cool!
>>>
>>> Would you care to ack it in its current form, knowing that we will fix
>>> it whenever we find a corner case interesting enough to study?
>>
>> I think just a little bit more polish is needed. I've just tried it out
>> and polish I can see is:
>>
>> 1. -h / --help with just a brief comment on what the tool does and usage.
>>
>> 2. Lead stats displayed for each cmdline argument with parsed filename.
>>
>> 3. Replace result section names "Single client", "Simulated clients" and
>> item names "total/ideal/packed" with a more descriptive text which would
>> hopefully be somewhat self-explanatory what the numbers represent.
>>
>> 4. Report garbage input (and unknown wsim commands) instead of reporting
>> some numbers for instance for ./sim_wsim README :)
>>
>> 5. #ifdef 0 graphviz ? add --graphviz cmddline option?
>>
>> 6. Oh.. and meson makefiles.. :)
>
> But if it was upstream, you would just contribute those improvements
> yourself.
>
> So you are saying that this is just not useful?
No, just that I think we have to have some minimum standard before we
can make it upstream. If you want I can implement these bits and send a
v3. Then it will just be a matter of finding a third person to review it
since we will both be authors. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-10 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 7:11 [Intel-gfx] [PATCH i-g-t] benchmarks/wsim: Simulate and interpret .wsim Chris Wilson
2018-05-11 7:11 ` Chris Wilson
2018-05-11 7:33 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-05-11 8:27 ` [Intel-gfx] [PATCH i-g-t] " Chris Wilson
2018-05-11 8:27 ` Chris Wilson
2018-05-11 8:31 ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-05-11 8:31 ` Tvrtko Ursulin
2018-05-11 9:04 ` [Intel-gfx] " Chris Wilson
2018-05-11 9:04 ` Chris Wilson
2018-05-11 9:21 ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-05-11 9:21 ` Tvrtko Ursulin
2018-05-11 9:33 ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-05-11 9:33 ` Chris Wilson
2018-05-11 11:56 ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-05-11 11:56 ` Tvrtko Ursulin
2018-07-10 13:47 ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-07-10 13:47 ` Chris Wilson
2018-07-10 15:38 ` [Intel-gfx] " Tvrtko Ursulin
2018-07-10 15:38 ` Tvrtko Ursulin
2018-07-10 15:40 ` [Intel-gfx] " Chris Wilson
2018-07-10 15:40 ` Chris Wilson
2018-07-10 16:05 ` Tvrtko Ursulin [this message]
2018-07-10 16:05 ` Tvrtko Ursulin
2018-05-11 8:45 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2018-05-11 9:46 ` [igt-dev] ✓ Fi.CI.BAT: success for benchmarks/wsim: Simulate and interpret .wsim (rev2) Patchwork
2018-05-11 11:24 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=b957c6d9-0c07-17a8-b965-fe0d1e9f19b4@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.