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 E0ACEC0218C for ; Mon, 27 Jan 2025 14:27:55 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 8B79D10E54E; Mon, 27 Jan 2025 14:27:55 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="mUCRxghx"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.19]) by gabe.freedesktop.org (Postfix) with ESMTPS id DA6AB10E23C for ; Mon, 27 Jan 2025 14:27:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1737988074; x=1769524074; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=JXu3C72/UuqamIjgVECrzCljBocR+l01mJkoHTld7vw=; b=mUCRxghxBVq+2U9ZNrvo9zBwYDvxBTKHCvOxwdrcys4YbMfoQdsGqJrQ BT6J1a8RlS4PZ9rnZpRzEgs5O9IkLeLzwqH3h1ku2ZLtfpt3du/7B75Du Qd7EMZmOh9kfY6Nv2uNI3npqS8lTwoedjifcqvjPWm2IVuI/IoPXTVbqL b+b06/ejJnefxAZnGj4z04bphNPzxwOZT15hSKauG6f26HayPJCDX+YHY FJ/yyHu1//RWdQnB3NoUFLP3E5+pM6LBbPisSp2rqZW9L+vmWq6tUiyzf SgTZi09JuaH1PBbR9YvdO4HX16Tf4UGAnD7wXT5ybGS6ybAeUoEY0k0QX Q==; X-CSE-ConnectionGUID: Fm7zd2lhQ6mQ5etyobe2jA== X-CSE-MsgGUID: Tj/izckQSy2p1PeQJlkXVw== X-IronPort-AV: E=McAfee;i="6700,10204,11328"; a="38333187" X-IronPort-AV: E=Sophos;i="6.13,238,1732608000"; d="scan'208";a="38333187" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jan 2025 06:27:53 -0800 X-CSE-ConnectionGUID: GSkDtyE0Q5a8D+X0XEAd3Q== X-CSE-MsgGUID: muplvx5tSkWY1CPBGSqQTA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,224,1728975600"; d="scan'208";a="108890670" Received: from nwochtma-mobl.ger.corp.intel.com (HELO friendship7-home.clients.intel.com) ([10.245.83.54]) by orviesa007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jan 2025 06:27:41 -0800 From: Peter Senna Tschudin To: igt-dev@lists.freedesktop.org Cc: Peter Senna Tschudin , stylon.wang@amd.com, Rodrigo.Siqueira@amd.com, ramadevi.gandi@intel.com, ryszard.knop@intel.com, sameer.lattannavar@intel.com, lucas.demarchi@intel.com, jani.saarinen@intel.com, katarzyna.piecielska@intel.com, matthew.d.roper@intel.com, gregory.f.germano@intel.com, clinton.a.taylor@intel.com, jianshui.yu@intel.com, balasubramani.vivekanandan@intel.com, jonathan.cavitt@intel.com Subject: [PATCH i-g-t v2 resend 0/2] Integrate kmemleak scans in igt_runner Date: Mon, 27 Jan 2025 15:27:34 +0100 Message-Id: <20250127142736.269756-1-peter.senna@linux.intel.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: igt-dev@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development mailing list for IGT GPU Tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: igt-dev-bounces@lists.freedesktop.org Sender: "igt-dev" This patch series introduces a library to interact with the Linux kernel's kmemleak feature and integrates it into igt_runner. If kmemleaks are detected, they will be saved in the igt_runner results directory in a file named kmemleak.txt. During testing, the size of the kmemleak.txt file varied significantly. Larger files, up to 2 MB, were observed when running i915-BAT on a Tiger Lake DUT. Conversely, smaller files, typically under 100 KB, were generated when running Xe BAT on the same DUT. Large files often contain numerous false positives, with the e1000 driver being a frequent source of noise. The time required for the Linux kernel to complete a kmemleak scan ranges from 5 to 60 seconds. This variability can cause igt_runner to slow down by a factor of 4 when using the -keach option. Transient leaks are a common phenomenon but are mostly undetected by the current version of this library. A typical transient leak occurs when pointers are reused, such as in linked lists. For example, if 10 calls to kmalloc are made, storing the address in the same variable and freeing only the final allocation, the previous 9 allocations become transient leaks. These leaks will go undetected unless the kernel thread performs continuous scanning. To enable continuous scanning: # echo scan=1 > /sys/kernel/debug/kmemleak This configures the kmemleak kernel thread to scan the memory continuously with 1 second pauses. While this may increase the likelihood of detecting transient leaks, it can significantly impact system performance. In most cases, the igt_runner slowdown remains in the 4x range, but the kernel thread will consume 100% of a CPU core, as observed with tools like top. When using scan=1, transient leaks that exist during an active scan will be detected. However, detection remains non-deterministic due to timing. It is recommended to reset the scan interval to the default value of 600 seconds after completing your tests. v2: - Pass igt_kmemleak_sync as a function variable to igt_kmemleak instead of keeping it stored as a global variable - igt_kmemleak_found_leaks(): Remove call to fseek() after close() - igt_kmemleak_write(): Increase retry counter when writing 0 bytes - igt_kmemleak_write(): change type to bool - Unit Testing: Move the call to igt_kmemleak_init() to a fixture. - igt_kmemleak_append_to(): Add brackets to the if statement for improved readability CC: stylon.wang@amd.com CC: Rodrigo.Siqueira@amd.com> CC: ramadevi.gandi@intel.com CC: ryszard.knop@intel.com CC: sameer.lattannavar@intel.com CC: lucas.demarchi@intel.com CC: jani.saarinen@intel.com CC: katarzyna.piecielska@intel.com CC: matthew.d.roper@intel.com CC: gregory.f.germano@intel.com CC: clinton.a.taylor@intel.com CC: jianshui.yu@intel.com CC: balasubramani.vivekanandan@intel.com CC: jonathan.cavitt@intel.com Peter Senna Tschudin (2): lib/igt_kmemleak: library to interact with kmemleak runner/executor: Integrate igt_kmemleak scans lib/igt_kmemleak.c | 274 +++++++++++++++++++++++++++++++++++++++ lib/igt_kmemleak.h | 16 +++ lib/meson.build | 1 + lib/tests/igt_kmemleak.c | 267 ++++++++++++++++++++++++++++++++++++++ lib/tests/meson.build | 1 + runner/executor.c | 25 +++- runner/runner_tests.c | 18 ++- runner/settings.c | 31 ++++- runner/settings.h | 2 + 9 files changed, 630 insertions(+), 5 deletions(-) create mode 100644 lib/igt_kmemleak.c create mode 100644 lib/igt_kmemleak.h create mode 100644 lib/tests/igt_kmemleak.c -- 2.34.1