Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 2/9] tests/i915/drm_fdinfo: Stress test context close versus fdinfo reads
Date: Mon, 6 Nov 2023 12:38:45 +0000	[thread overview]
Message-ID: <710eaf92-46d5-42e8-9c46-b59571401494@linux.intel.com> (raw)
In-Reply-To: <20231103183254.kl4uhqzbfw7nw6i4@kamilkon-desk.igk.intel.com>


On 03/11/2023 18:32, Kamil Konieczny wrote:
> Hi Tvrtko,
> On 2023-10-12 at 09:15:40 +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> A short smoke tests to exercise fdinfo reads in parallel to contexts
>> getting created and destroyed.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>>   tests/intel/drm_fdinfo.c | 68 ++++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 68 insertions(+)
>>
>> diff --git a/tests/intel/drm_fdinfo.c b/tests/intel/drm_fdinfo.c
>> index 344c44dce78b..c4218b0d16e6 100644
>> --- a/tests/intel/drm_fdinfo.c
>> +++ b/tests/intel/drm_fdinfo.c
>> @@ -22,11 +22,14 @@
>>    *
>>    */
>>   
>> +#include <fcntl.h>
>> +
>>   #include "igt.h"
>>   #include "igt_core.h"
>>   #include "igt_device.h"
>>   #include "igt_drm_fdinfo.h"
>>   #include "i915/gem.h"
>> +#include "i915/gem_create.h"
>>   #include "i915/gem_vm.h"
>>   #include "intel_ctx.h"
>>   /**
>> @@ -72,6 +75,8 @@
>>    * SUBTEST: virtual-busy-idle-all
>>    *
>>    * SUBTEST: virtual-idle
>> + *
>> + * SUBTEST: context-close-stress
>>    */
>>   
>>   IGT_TEST_DESCRIPTION("Test the i915 drm fdinfo data");
>> @@ -717,6 +722,56 @@ virtual_all(int i915, const intel_ctx_cfg_t *base_cfg, unsigned int flags)
>>   	}
>>   }
>>   
>> +static void stress_context_close(int i915)
>> +{
>> +	const uint32_t bbe = MI_BATCH_BUFFER_END;
>> +	struct igt_helper_process reader = { };
>> +	struct drm_client_fdinfo info;
>> +	uint32_t batch;
>> +	int dir, ret;
>> +	char buf[64];
>> +
>> +	ret = snprintf(buf, sizeof(buf), "%u", i915);
>> +	igt_assert(ret > 0 && ret < sizeof(buf));
>> +
>> +	dir = open("/proc/self/fdinfo", O_DIRECTORY | O_RDONLY);
>> +	igt_assert_fd(dir);
>> +
>> +	memset(&info, 0, sizeof(info));
>> +	ret = __igt_parse_drm_fdinfo(dir, buf, &info, NULL, 0, NULL, 0);
>> +	igt_assert(ret > 0);
> 
> You repeat this pattern later, it can be made into
> function:
> 
> igt_parse_drm_fdinfo(dir, buf, *info, p1, i1, p2, i2)
> {
> 	memset(info, 0, sizeof(*info));
> 	ret = __igt_parse_drm_fdinfo(dir, buf, info, p1, i1, p2, i2);
> 	igt_assert(ret > 0);
> }
> 
>> +	igt_require(info.num_regions);
>> +
>> +	batch = gem_create(i915, 4096);
>> +	gem_write(i915, batch, 0, &bbe, sizeof(bbe));
>> +
>> +	igt_fork_helper(&reader) {
>> +		for (;;) {
>> +			memset(&info, 0, sizeof(info));
>> +			ret = __igt_parse_drm_fdinfo(dir, buf, &info,
>> +						     NULL, 0, NULL, 0);
>> +			igt_assert(ret > 0);
> 
> Here you repeat this.
> 
> With or without makeing this a function,
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>

Thanks Kamil!

I opted to keep it as is to avoid having to come with a name for a new 
helper, and because it is only two instances.

Doing another CI pass on both IGT and i915 series and fingers crossed it 
is still all healthy.

Regards,

Tvrtko

> 
>> +		}
>> +	}
>> +
>> +	igt_until_timeout(10) {
>> +		struct drm_i915_gem_exec_object2 obj = {
>> +			.handle = batch,
>> +		};
>> +		struct drm_i915_gem_execbuffer2 eb = {
>> +			.buffers_ptr = to_user_pointer(&obj),
>> +			.buffer_count = 1,
>> +		};
>> +
>> +		eb.rsvd1 = gem_context_create(i915);
>> +		igt_assert(eb.rsvd1);
>> +		gem_execbuf(i915, &eb);
>> +		gem_context_destroy(i915, eb.rsvd1);
>> +	}
>> +
>> +	igt_stop_helper(&reader);
>> +}
>> +
>>   #define test_each_engine(T, i915, ctx, e) \
>>   	igt_subtest_with_dynamic(T) for_each_ctx_engine(i915, ctx, e) \
>>   		igt_dynamic_f("%s", e->name)
>> @@ -848,6 +903,19 @@ igt_main
>>   	test_each_engine("isolation", i915, ctx, e)
>>   		single(i915, ctx, e, TEST_BUSY | TEST_ISOLATION);
>>   
>> +	igt_subtest_group {
>> +		int newfd;
>> +
>> +		igt_fixture
>> +			newfd = drm_reopen_driver(i915);
>> +
>> +		igt_subtest("context-close-stress")
>> +			stress_context_close(newfd);
>> +
>> +		igt_fixture
>> +			drm_close_driver(newfd);
>> +	}
>> +
>>   	igt_fixture {
>>   		intel_ctx_destroy(i915, ctx);
>>   		drm_close_driver(i915);
>> -- 
>> 2.39.2
>>

  reply	other threads:[~2023-11-06 12:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  8:15 [igt-dev] [PATCH i-g-t 0/9] Client memory fdinfo test and intel_gpu_top support Tvrtko Ursulin
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 1/9] tests/i915/drm_fdinfo: Check engine info is supported Tvrtko Ursulin
2023-11-03 18:21   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 2/9] tests/i915/drm_fdinfo: Stress test context close versus fdinfo reads Tvrtko Ursulin
2023-11-03 18:32   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-11-06 12:38     ` Tvrtko Ursulin [this message]
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 3/9] tests/i915/drm_fdinfo: Add some memory info tests Tvrtko Ursulin
2023-11-03 19:05   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 4/9] lib/igt_drm_fdinfo: Copy over region map name on match Tvrtko Ursulin
2023-11-03 18:56   ` Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 5/9] lib/igt_drm_clients: Fix client id type confusion Tvrtko Ursulin
2023-11-03 18:54   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 6/9] lib/igt_drm_clients: Allow passing in the memory region map Tvrtko Ursulin
2023-11-03 18:47   ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 7/9] tools/intel_gpu_top: Fully wrap clients operations Tvrtko Ursulin
2023-11-03 18:57   ` Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 8/9] tools/intel_gpu_top: Add per client memory info Tvrtko Ursulin
2023-11-03 19:01   ` Kamil Konieczny
2023-10-12  8:15 ` [igt-dev] [PATCH i-g-t 9/9] tools/intel_gpu_top: Add ability to show memory region breakdown Tvrtko Ursulin
2023-11-03 19:04   ` Kamil Konieczny
2023-10-12 15:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Client memory fdinfo test and intel_gpu_top support (rev2) Patchwork
2023-10-12 15:29 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-13 13:18 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-06 12:41   ` Kamil Konieczny
2023-11-07 12:59     ` Illipilli, TejasreeX
2023-11-07 12:28 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2023-11-07 12:36 ` 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=710eaf92-46d5-42e8-9c46-b59571401494@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=tvrtko.ursulin@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