[PATCH i-g-t 4/4] lib/xe_eudebug: Increase default pipe timeout value

[Mika Kuoppala <mika.kuoppala@linux.intel.com>]

Our discovery tests are quite heavy, there can be tens of
threads of clients and debuggers racing against eachothers.

If there are lots of debugs enabled in kernel config, it is
in real of possibility to end up in a situation where one
client or one debugger really was starved more than 25 seconds.

This timeout is used in communication between test framework,
debuggers and debuggees and thus if we timeout on it,
it will lead to confusing errors in middle tests.

The tradeoff is that for really failing tests where the
other endpoint ceases to respond, we will detect that now
slower.

Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
---
 lib/xe/xe_eudebug.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/xe/xe_eudebug.h b/lib/xe/xe_eudebug.h
index 29ab68fee..6e4666333 100644
--- a/lib/xe/xe_eudebug.h
+++ b/lib/xe/xe_eudebug.h
@@ -112,7 +112,7 @@ typedef void (*xe_eudebug_trigger_fn)(struct xe_eudebug_debugger *,
  * Default abort timeout to use across xe_eudebug lib and tests if no specific
  * timeout value is required.
  */
-#define XE_EUDEBUG_DEFAULT_TIMEOUT_SEC		25ULL
+#define XE_EUDEBUG_DEFAULT_TIMEOUT_SEC		60ULL
 
 #define XE_EUDEBUG_FILTER_EVENT_NONE		BIT(DRM_XE_EUDEBUG_EVENT_NONE)
 #define XE_EUDEBUG_FILTER_EVENT_READ		BIT(DRM_XE_EUDEBUG_EVENT_READ)
-- 
2.34.1