Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karolina Drobnik <karolina.drobnik@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2 2/3] lib/intel_batchbuffer: Add support for custom engine layouts
Date: Tue, 25 Oct 2022 14:29:07 +0200	[thread overview]
Message-ID: <d6210119-5533-d4ba-e795-b165aec0decf@intel.com> (raw)
In-Reply-To: <Y1ep9FTpDzaUYCFO@zkempczy-mobl2>

On 25.10.2022 11:18, Zbigniew Kempczyński wrote:
> On Tue, Oct 25, 2022 at 09:15:00AM +0200, Karolina Drobnik wrote:
>> Don't assume fixed engine ids and use context configuration in
>> intel_bb to find the appropriate engine when executing the batchbuffer.
>>
>> Signed-off-by: Karolina Drobnik <karolina.drobnik@intel.com>
>> ---
>>   lib/intel_batchbuffer.c | 49 ++++++++++++++++++++++++++++++++++-------
>>   1 file changed, 41 insertions(+), 8 deletions(-)
>>
>> diff --git a/lib/intel_batchbuffer.c b/lib/intel_batchbuffer.c
>> index 0b18f86a..5358b82b 100644
>> --- a/lib/intel_batchbuffer.c
>> +++ b/lib/intel_batchbuffer.c
>> @@ -1491,6 +1491,29 @@ static bool aux_needs_softpin(int i915)
>>   	return intel_gen(intel_get_drm_devid(i915)) >= 12;
>>   }
>>   
>> +static bool has_ctx_cfg(struct intel_bb *ibb)
>> +{
>> +	return ibb->cfg && (ibb->cfg->num_engines > 0);
> 
> Brackets are not necessary.

I added them to improve readability. Can remove them, no problem.

>> +}
>> +
>> +static uint32_t find_engine(struct intel_bb *ibb, unsigned int class)
>> +{
>> +	intel_ctx_cfg_t *cfg;
>> +	unsigned int i;
>> +	uint32_t engine_id = -1;
>> +
>> +	cfg = ibb->cfg;
>> +	for (i = 0; i < cfg->num_engines; i++) {
>> +		if (cfg->engines[i].engine_class == class)
>> +			engine_id = i;
>> +	}
>> +
>> +	/* Make sure we actually found the engine */
>> +	igt_assert(engine_id != -1);
> 
> Add some info what's wrong here with igt_assert_f().

Good call, I forgot about that helper.

> 
> With above fixed:
> 
> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> 

Thanks,
Karolina

> --
> Zbigniew
>> +
>> +	return engine_id;
>> +}
>> +
>>   /**
>>    * intel_bb_create:
>>    * @i915: drm fd
>> @@ -2792,34 +2815,44 @@ void intel_bb_flush(struct intel_bb *ibb, uint32_t ring)
>>    * intel_bb_flush_render:
>>    * @ibb: batchbuffer
>>    *
>> - * If batch is not empty emit batch buffer end, execute on render ring
>> - * and reset the batch. Context used to execute is batch context.
>> + * If batch is not empty emit batch buffer end, find the render engine id,
>> + * execute on the ring and reset the batch. Context used to execute
>> + * is batch context.
>>    */
>>   void intel_bb_flush_render(struct intel_bb *ibb)
>>   {
>> +	uint32_t ring;
>> +
>>   	if (intel_bb_emit_flush_common(ibb) == 0)
>>   		return;
>>   
>> -	intel_bb_exec_with_ring(ibb, I915_EXEC_RENDER);
>> +	if (has_ctx_cfg(ibb))
>> +		ring = find_engine(ibb, I915_ENGINE_CLASS_RENDER);
>> +	else
>> +		ring = I915_EXEC_RENDER;
>> +
>> +	intel_bb_exec_with_ring(ibb, ring);
>>   }
>>   
>>   /*
>>    * intel_bb_flush_blit:
>>    * @ibb: batchbuffer
>>    *
>> - * If batch is not empty emit batch buffer end, execute on default/blit ring
>> - * (depends on gen) and reset the batch.
>> + * If batch is not empty emit batch buffer end, find a suitable ring
>> + * (depending on gen and context configuration) and reset the batch.
>>    * Context used to execute is batch context.
>>    */
>>   void intel_bb_flush_blit(struct intel_bb *ibb)
>>   {
>> -	uint32_t ring = I915_EXEC_DEFAULT;
>> +	uint32_t ring;
>>   
>>   	if (intel_bb_emit_flush_common(ibb) == 0)
>>   		return;
>>   
>> -	if (HAS_BLT_RING(ibb->devid))
>> -		ring = I915_EXEC_BLT;
>> +	if (has_ctx_cfg(ibb))
>> +		ring = find_engine(ibb, I915_ENGINE_CLASS_COPY);
>> +	else
>> +		ring = HAS_BLT_RING(ibb->devid) ? I915_EXEC_BLT : I915_EXEC_DEFAULT;
>>   
>>   	intel_bb_exec_with_ring(ibb, ring);
>>   }
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2022-10-25 12:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  7:14 [igt-dev] [PATCH i-g-t v2 0/3] Add support for intel_ctx_t in intel_bb Karolina Drobnik
2022-10-25  7:14 ` [igt-dev] [PATCH i-g-t v2 1/3] lib/intel_batchbuffer: Extend __intel_bb_create to handle context config Karolina Drobnik
2022-10-25  9:00   ` Zbigniew Kempczyński
2022-10-25 12:25     ` Karolina Drobnik
2022-10-25  7:15 ` [igt-dev] [PATCH i-g-t v2 2/3] lib/intel_batchbuffer: Add support for custom engine layouts Karolina Drobnik
2022-10-25  9:18   ` Zbigniew Kempczyński
2022-10-25 12:29     ` Karolina Drobnik [this message]
2022-10-25  7:15 ` [igt-dev] [PATCH i-g-t v2 3/3] tests/api_intel_bb: Add misplaced_blitter test Karolina Drobnik
2022-10-25  8:54   ` Zbigniew Kempczyński
2022-10-25 12:33     ` Karolina Drobnik
2022-10-25 12:49       ` Zbigniew Kempczyński
2022-10-25 12:53         ` Petri Latvala
2022-10-25 14:10           ` Karolina Drobnik
2022-10-25 14:08         ` Karolina Drobnik
2022-10-25 15:54           ` Zbigniew Kempczyński
2022-10-25  8:15 ` [igt-dev] ✗ Fi.CI.BAT: failure for Add support for intel_ctx_t in intel_bb (rev2) Patchwork
2022-10-25  8:31   ` Karolina Drobnik
2022-10-25 17:22     ` Vudum, Lakshminarayana
2022-10-25 15:28 ` Patchwork
2022-10-25 16:09 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-10-25 23:37 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=d6210119-5533-d4ba-e795-b165aec0decf@intel.com \
    --to=karolina.drobnik@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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