From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E2634C38142 for ; Tue, 31 Jan 2023 16:19:52 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 3264110E092; Tue, 31 Jan 2023 16:19:52 +0000 (UTC) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTPS id 19F4C10E06A; Tue, 31 Jan 2023 16:19:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675181990; x=1706717990; h=date:message-id:from:to:cc:subject:in-reply-to: references:mime-version; bh=+wy3AS5Xpy6pW7yHM4qA2hfPXKf7XBiA3jIKYsVIMZQ=; b=V5PZlNFvhQo4g0Oz0/VBleaQLDBJl/2lQ+gX03bpS0QKwqfyVS6PVKjs 3eTB9VqgfP1tdZU/Fpa4jwJkj/1vgt5fQVQZYol3IJumnjEoJuKimu9eB PkVxO1TEW9xwHreQ1g+OsnIoOtO+37YacgRJwAIDg9YeMSCPPoeBpost1 Y5aAdqCV5Gh2O8GsrRlxJbC9dGETWmHvqqEhZYP0OjblbO2JT9osJ3Flu MJj+nXO93PRPDc+dflaJZEVflr5gSm7mciI9SgcdbO9txTcTucslezFbQ ohHm9l2FtypUj8Zqm8+ElUngNRagL5C946x38j7MAiFcVOVkfiz9ANVyQ Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10606"; a="329153182" X-IronPort-AV: E=Sophos;i="5.97,261,1669104000"; d="scan'208";a="329153182" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jan 2023 08:19:49 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10606"; a="993330779" X-IronPort-AV: E=Sophos;i="5.97,261,1669104000"; d="scan'208";a="993330779" Received: from tburnham-mobl.amr.corp.intel.com (HELO adixit-arch.intel.com) ([10.209.70.92]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jan 2023 08:19:48 -0800 Date: Tue, 31 Jan 2023 08:19:48 -0800 Message-ID: <87a61yvfq3.wl-ashutosh.dixit@intel.com> From: "Dixit, Ashutosh" To: Janusz Krzysztofik In-Reply-To: <20230131091731.5892-1-janusz.krzysztofik@linux.intel.com> References: <20230131091731.5892-1-janusz.krzysztofik@linux.intel.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.2 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Subject: Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 0/2] tests/i915/perf: Add stress / race exercises X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: igt-dev@lists.freedesktop.org, Arkadiusz Hiler , intel-gfx@lists.freedesktop.org, Petri Latvala , Chris Wilson Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Tue, 31 Jan 2023 01:17:29 -0800, Janusz Krzysztofik wrote: > Hi Janusz, > Users reported oopses on list corruptions when using i915 perf with a > number of concurrently running graphics applications. That indicates we > are currently missing some important tests for such scenarios. Cover > that gap. Do these oops etc. have anything to do with perf itself or rather with persistence or non-persistence not properly supported with GuC? We should have seen such failures with persistence tests (with GuC) itself so I am wondering if there's any point of dragging perf into these already muddy waters? Such failures should be isolated first with other tests without mixing perf into this IMO. Thanks. -- Ashutosh