All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_frontbuffer_tracking: Reduce fbc status spam, v2.
Date: Thu, 15 Mar 2018 19:43:45 +0100	[thread overview]
Message-ID: <69520d8e-40a4-1997-c440-79c1279d7a97@linux.intel.com> (raw)
In-Reply-To: <152111360520.16598.5961832428973099816@mail.alporthouse.com>

Op 15-03-18 om 12:33 schreef Chris Wilson:
> Quoting Maarten Lankhorst (2018-03-15 11:26:55)
>> When FBC cannot be enabled in one of the tests, we get a lot of repeated
>> spam at DEBUG level, which overwrites any good debug level data that you
>> can hope to get out of the test.
>>
>> When running at the debug level, output FBC info only if changed from last
>> time, so we don't get the repeated spam.
>>
>> This makes the debug info from CI slightly more useful.
>>
>> Changes since v1:
>> - Clear last_fbc_buf in fbc_wait_until_enabled.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> ---
>> diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
>> index 06b34ddb90b4..2b85392dfa4b 100644
>> --- a/tests/kms_frontbuffer_tracking.c
>> +++ b/tests/kms_frontbuffer_tracking.c
>> @@ -755,12 +755,24 @@ static int __debugfs_write(const char *param, char *buf, int len)
>>  #define debugfs_read(p, arr) __debugfs_read(p, arr, sizeof(arr))
>>  #define debugfs_write(p, arr) __debugfs_write(p, arr, sizeof(arr))
>>  
>> +static char last_fbc_buf[128];
>> +
>>  static bool fbc_is_enabled(int lvl)
>>  {
>>         char buf[128];
>> +       bool print = true;
>>  
>>         debugfs_read("i915_fbc_status", buf);
>> -       igt_log(IGT_LOG_DOMAIN, lvl, "fbc_is_enabled()?\n%s", buf);
>> +       if (lvl != IGT_LOG_DEBUG)
>> +               last_fbc_buf[0] = '\0';
>> +       else if (strcmp(last_fbc_buf, buf))
>> +               strcpy(last_fbc_buf, buf);
>> +       else
>> +               print = false;
>> +
>> +       if (print)
>> +               igt_log(IGT_LOG_DOMAIN, lvl, "fbc_is_enabled()?\n%s", buf);
>> +
>>         return strstr(buf, "FBC enabled\n");
>>  }
>>  
>> @@ -945,6 +957,8 @@ static bool fbc_stride_not_supported(void)
>>  
>>  static bool fbc_wait_until_enabled(void)
>>  {
>> +       last_fbc_buf[0] = '\0';
>> +
>>         return igt_wait(fbc_is_enabled(IGT_LOG_DEBUG), 2000, 1);
>>  }
> Without the stray,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris

Thanks, pushed. :)

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

  reply	other threads:[~2018-03-15 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 11:00 [igt-dev] [PATCH i-g-t] tests/kms_frontbuffer_tracking: Reduce fbc status spam Maarten Lankhorst
2018-03-15 11:06 ` Chris Wilson
2018-03-15 11:26   ` [igt-dev] [PATCH i-g-t] tests/kms_frontbuffer_tracking: Reduce fbc status spam, v2 Maarten Lankhorst
2018-03-15 11:33     ` Chris Wilson
2018-03-15 18:43       ` Maarten Lankhorst [this message]
2018-03-15 13:01 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_frontbuffer_tracking: Reduce fbc status spam. (rev2) Patchwork
2018-03-15 14:41 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-03-15 17:49 ` [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=69520d8e-40a4-1997-c440-79c1279d7a97@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.