public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi@etezian.org>
Cc: IGT dev <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v21 6/6] test: perf_pmu: use the gem_engine_topology library
Date: Wed, 17 Apr 2019 14:42:31 +0100	[thread overview]
Message-ID: <0f2526fc-d0d3-c34a-24a2-fb90ed648ed4@linux.intel.com> (raw)
In-Reply-To: <20190416230511.GA14233@jack.zhora.eu>


On 17/04/2019 00:05, Andi Shyti wrote:
>>> @@ -1046,14 +1057,18 @@ static void cpu_hotplug(int gem_fd)
>>>    	igt_require(cpu0_hotplug_support());
>>> +	ctx = gem_context_create(gem_fd);
>>
>> TODO left was to try without new contexts for a handful of tests where I
>> added them. Instead try I915_EXEC_DEFAULT when submitting and (ab)use the
>> fact RCS is at index zero for foreseeable future. When it fails we'll know
>> about it. This applies to hotplug, frequency, interrupts subtests AFAIR.
> 
> yes, I was also thinking about adding a few wrappers around.

I'm afraid I lost you here, I did not mention any wrappers here? I was 
thinking about the thing we talked about before, where I knee-jerk added 
context creation to some subtests and have later realized we could 
possibly do without that.

> I managed to build quite a hefty list of things to do in these 21
> versions (22 with the coming)

Next time you can occasionally send updated individual patches as 
--in-reply-to instead of resending the whole series which would keep the 
cover letter change log smaller. ;)

You only need to send the whole series when there are new or removed 
patches, if the time delay between posts is long, or if there was as 
rebase/conflict due base moving. Or if the reply chain gets too long. 
Those are my guidelines anyway, I don't claim they are somewhere 
documented or match other people opinions.

> But I would happily send them once this series gets accepted to
> not procrastinate it further.

In my view it is basically almost there and accepted in principle, just 
needs some final tweaks.

Regards,

Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-04-17 13:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 15:11 [igt-dev] [PATCH v21 0/6] new engine discovery interface Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 1/6] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 2/6] lib/i915: add gem_engine_topology library and for_each loop definition Andi Shyti
2019-04-16 15:21   ` Chris Wilson
2019-04-16 15:28     ` Andi Shyti
2019-04-16 17:09       ` Tvrtko Ursulin
2019-04-16 15:11 ` [igt-dev] [PATCH v21 3/6] lib: igt_gt: add execution buffer flags to class helper Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 4/6] lib: igt_gt: make gem_engine_can_store_dword() check engine class Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 5/6] lib: igt_dummyload: use for_each_context_engine() Andi Shyti
2019-04-17 15:42   ` Daniele Ceraolo Spurio
2019-04-17 15:48     ` Chris Wilson
2019-04-17 16:14     ` Tvrtko Ursulin
2019-04-17 16:21       ` Chris Wilson
2019-04-18  8:46         ` Tvrtko Ursulin
2019-04-16 15:11 ` [igt-dev] [PATCH v21 6/6] test: perf_pmu: use the gem_engine_topology library Andi Shyti
2019-04-16 17:06   ` Tvrtko Ursulin
2019-04-16 23:05     ` Andi Shyti
2019-04-17 13:42       ` Tvrtko Ursulin [this message]
2019-04-16 16:36 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-04-17  0:46 ` [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=0f2526fc-d0d3-c34a-24a2-fb90ed648ed4@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=andi@etezian.org \
    --cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox