<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT][guc] igt@debugfs_test@read_all_entries_display_off - dmesg-warn - WARN_ON(!intel_guc_log_relay_enabled(log))" href="https://bugs.freedesktop.org/show_bug.cgi?id=111165#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT][guc] igt@debugfs_test@read_all_entries_display_off - dmesg-warn - WARN_ON(!intel_guc_log_relay_enabled(log))" href="https://bugs.freedesktop.org/show_bug.cgi?id=111165">bug 111165</a> from <a class="email" href="mailto:jon.ewins@intel.com" title="Jon Ewins <jon.ewins@intel.com>"> Jon Ewins</a> <pre>The relay log is a developer only feature and an extension of the standard GuC logging mechanism. Its testing should not be part of the BAT set. It is being implicitly enabled by existing tests, which provide no consumer for the logs. The issue is that IGT tests that cycle through reading the debugfs entries will call the open file op for the guc_log_relay control file and this currently causes the file to be both created and the logging to be started. These tests have no consumer for the logs which go on to overflow, run out of sub-buffers or misbehave in suspend and reset handling. A proposed change, that will follow as RFC patches, is to separate the creation and logging start, updating the guc_log_relay_write function, which currently just flushes the log, to also support starting the logging based on the value written. An additional new test to actually explicitly test this relay log developer feature will follow separately.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>