From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/perf: add a test for OA data polling reads using "small" buffers
Date: Thu, 26 Mar 2020 11:02:40 +0200 [thread overview]
Message-ID: <ceae76dd-d0e4-3c30-8541-04c54648dc79@intel.com> (raw)
In-Reply-To: <0a297819cd4a3fe8fcc9f5f6e03d7d0ee7b4ac3c.1585201183.git.ashutosh.dixit@intel.com>
On 26/03/2020 07:42, Ashutosh Dixit wrote:
> Add a test for OA data non-blocking reads using buffers smaller than
> the available data. This test would fail for perf revisions < 5
> because poll would block even when data was available. Therefore the
> amount of data read was limited by the buffer size and the timer
> interval and it was impossible to read all available data. This issue
> is fixed in perf revision 5.
There seems to be a fundamental issue with this test, it's supposed to
test a broken behavior with revision < 5 but then avoid testing anything
there ;)
I've modified this test a bit here :
https://gitlab.freedesktop.org/llandwerlin/igt-gpu-tools/-/tree/for-ashutosh
It's failing stable kernels.
Increasing the size of the buffer to 1Mb make the test pass.
-Lionel
>
> Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Signed-off--by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> tests/perf.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 81 insertions(+)
>
> diff --git a/tests/perf.c b/tests/perf.c
> index 724f6f809..41e3b4478 100644
> --- a/tests/perf.c
> +++ b/tests/perf.c
> @@ -2265,6 +2265,81 @@ test_polling(void)
> __perf_close(stream_fd);
> }
>
> +static void test_polling_small_buf(void)
> +{
> + int oa_exponent = max_oa_exponent_for_period_lte(10 * 1000 * 1000); /* 10ms */
> + /* Use a large value for the timer for a large amout of data to accumulate */
> + uint64_t kernel_hrtimer = 400 * 1000 * 1000; /* 400 ms */
> + uint64_t properties[] = {
> + /* Include OA reports in samples */
> + DRM_I915_PERF_PROP_SAMPLE_OA, true,
> +
> + /* OA unit configuration */
> + DRM_I915_PERF_PROP_OA_METRICS_SET, test_set->perf_oa_metrics_set,
> + DRM_I915_PERF_PROP_OA_FORMAT, test_set->perf_oa_format,
> + DRM_I915_PERF_PROP_OA_EXPONENT, oa_exponent,
> +
> + /* Kernel configuration (optional) */
> + DRM_I915_PERF_PROP_POLL_OA_PERIOD, kernel_hrtimer,
> + };
> + struct drm_i915_perf_open_param param = {
> + .flags = I915_PERF_FLAG_FD_CLOEXEC |
> + I915_PERF_FLAG_DISABLED |
> + I915_PERF_FLAG_FD_NONBLOCK,
> + .num_properties = NUM_PROPERTIES(properties),
> + .properties_ptr = to_user_pointer(properties),
> + };
> + uint8_t buf[1024 * 1024];
> + int ret, iterl = 0, iters = 0, large = 0, small = 0;
> + struct timespec tsl = {}, tss = {};
> +
> + stream_fd = __perf_open(drm_fd, ¶m, true /* prevent_pm */);
> + do_ioctl(stream_fd, I915_PERF_IOCTL_ENABLE, 0);
> +
> + /* First do non blocking reads for 4 seconds using 1 MB buffer */
> + igt_nsec_elapsed(&tsl);
> + igt_until_timeout(4) {
> + struct pollfd pollfd = { .fd = stream_fd, .events = POLLIN };
> +
> + ret = poll(&pollfd, 1, -1);
> + igt_assert_eq(ret, 1);
> + igt_assert(pollfd.revents & POLLIN);
> +
> + ret = read(stream_fd, buf, sizeof(buf));
> + igt_assert(ret > 0);
> + large += ret;
> + iterl++;
> + }
> + igt_debug("Read %d B in %d iterations in %ld ns using 1 MB buffer\n",
> + large, iterl, igt_nsec_elapsed(&tsl));
> +
> + /* Now repeat the read with a 4 KB buffer */
> + igt_nsec_elapsed(&tss);
> + igt_until_timeout(4) {
> + struct pollfd pollfd = { .fd = stream_fd, .events = POLLIN };
> +
> + ret = poll(&pollfd, 1, -1);
> + igt_assert_eq(ret, 1);
> + igt_assert(pollfd.revents & POLLIN);
> +
> + ret = read(stream_fd, buf, 4096);
> + igt_assert(ret > 0);
> + small += ret;
> + iters++;
> + }
> + igt_debug("Read %d B in %d iterations in %ld ns using 4 KB buffer\n",
> + small, iters, igt_nsec_elapsed(&tss));
> +
> + __perf_close(stream_fd);
> +
> + /* Check that data read using the two methods is within 20% of each
> + * other. Differences between the two cases is due to timing coupled
> + * with granularity of the data reads, but they are still expected to be
> + * "close".
> + */
> + igt_assert(abs(large - small) * 100 / ((large + small) / 2) < 20);
> +}
> +
> static int
> num_valid_reports_captured(struct drm_i915_perf_open_param *param,
> int64_t *duration_ns)
> @@ -4676,6 +4751,12 @@ igt_main
> igt_subtest("polling")
> test_polling();
>
> + igt_describe("Test polled read with buffer size smaller than available data");
> + igt_subtest("polling-small-buf") {
> + igt_require(i915_perf_revision(drm_fd) >= 5);
> + test_polling_small_buf();
> + }
> +
> igt_subtest("short-reads")
> test_short_reads();
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-03-26 9:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 5:42 [igt-dev] [PATCH i-g-t] tests/perf: add a test for OA data polling reads using "small" buffers Ashutosh Dixit
2020-03-26 5:52 ` [igt-dev] ✗ Fi.CI.BUILD: failure for " Patchwork
2020-03-26 6:01 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2020-03-26 9:02 ` Lionel Landwerlin [this message]
2020-03-27 4:08 ` [igt-dev] [PATCH i-g-t] " Dixit, Ashutosh
-- strict thread matches above, loose matches on Subject: below --
2020-03-27 4:42 Ashutosh Dixit
2020-03-27 4:50 ` Dixit, Ashutosh
2020-03-27 16:09 ` Lionel Landwerlin
2020-03-27 19:03 ` Dixit, Ashutosh
2020-03-27 19:06 ` Lionel Landwerlin
2020-03-27 19:49 ` Dixit, Ashutosh
2020-03-31 6:06 ` Dixit, Ashutosh
2020-03-31 7:36 ` Lionel Landwerlin
2020-03-31 7:48 ` Dixit, Ashutosh
2020-04-03 1:19 ` Dixit, Ashutosh
2020-03-27 20:56 ` Umesh Nerlige Ramappa
2020-03-27 22:02 ` Dixit, Ashutosh
2020-03-27 22:29 Ashutosh Dixit
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=ceae76dd-d0e4-3c30-8541-04c54648dc79@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=ashutosh.dixit@intel.com \
--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