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 picard.linux.it (picard.linux.it [213.254.12.146]) (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 3A78FD609C1 for ; Wed, 27 Nov 2024 09:46:18 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id AC2A73DB5A0 for ; Wed, 27 Nov 2024 10:46:16 +0100 (CET) Received: from in-3.smtp.seeweb.it (in-3.smtp.seeweb.it [217.194.8.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1)) (No client certificate requested) by picard.linux.it (Postfix) with ESMTPS id 530553DB35F for ; Wed, 27 Nov 2024 10:46:02 +0100 (CET) Authentication-Results: in-3.smtp.seeweb.it; spf=pass (sender SPF authorized) smtp.mailfrom=suse.cz (client-ip=195.135.223.131; helo=smtp-out2.suse.de; envelope-from=chrubis@suse.cz; receiver=lists.linux.it) Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.223.131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by in-3.smtp.seeweb.it (Postfix) with ESMTPS id C4F2B1BDD066 for ; Wed, 27 Nov 2024 10:46:01 +0100 (CET) Received: from imap1.dmz-prg2.suse.org (imap1.dmz-prg2.suse.org [IPv6:2a07:de40:b281:104:10:150:64:97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 85A281F76C; Wed, 27 Nov 2024 09:46:00 +0000 (UTC) Authentication-Results: smtp-out2.suse.de; none Received: from imap1.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap1.dmz-prg2.suse.org (Postfix) with ESMTPS id 73288139AA; Wed, 27 Nov 2024 09:46:00 +0000 (UTC) Received: from dovecot-director2.suse.de ([2a07:de40:b281:106:10:150:64:167]) by imap1.dmz-prg2.suse.org with ESMTPSA id B+IUG1jqRmcyQgAAD6G6ig (envelope-from ); Wed, 27 Nov 2024 09:46:00 +0000 Date: Wed, 27 Nov 2024 10:46:12 +0100 From: Cyril Hrubis To: Li Wang Message-ID: References: <20241126100445.17133-1-liwang@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 50.00]; REPLY(-4.00)[]; ASN(0.00)[asn:25478, ipnet:::/0, country:RU] X-Rspamd-Queue-Id: 85A281F76C X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Action: no action X-Rspamd-Server: rspamd1.dmz-prg2.suse.org X-Virus-Scanned: clamav-milter 1.0.3 at in-3.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime X-BeenThere: ltp@lists.linux.it X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Test Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Philip Auld , ltp@lists.linux.it Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-bounces+ltp=archiver.kernel.org@lists.linux.it Sender: "ltp" Hi! > I have carefully compared the differences between the general > kernel config-file and the debug kernel config-file. > > Below are some configurations that are only enabled in the debug > kernel and may cause kernel performance degradation. > > The rough thoughts I have is to create a SET for those configurations, > If the SUT kernel maps some of them, we reset the timeout using the > value multiplier obtained from calibration. > > e.g. if mapped N number of the configs we use (timeout * N) as the > max_runtime. > > Or next, we extract this method to the whole LTP timeout setting if > possible? That actually sounds good to me, if we detect certain kernel options that are know to slow down the process execution it makes a good sense to multiply the timeouts for all tests directly in the test library. > #Lock debugging: > CONFIG_PROVE_LOCKING > CONFIG_LOCKDEP > CONFIG_DEBUG_SPINLOCK > > #Mutex debugging > CONFIG_DEBUG_RT_MUTEXES=y > CONFIG_DEBUG_MUTEXES=y > > #Memory debugging: > CONFIG_DEBUG_PAGEALLOC > CONFIG_KASAN > CONFIG_SLUB_RCU_DEBUG > > #Tracing and profiling: > CONFIG_TRACE_IRQFLAGS > CONFIG_LATENCYTOP > CONFIG_DEBUG_NET > > #Filesystem debugging: > CONFIG_EXT4_DEBUG > CONFIG_QUOTA_DEBUG > > #Miscellaneous debugging: > CONFIG_FAULT_INJECTION > CONFIG_DEBUG_OBJECTS -- Cyril Hrubis chrubis@suse.cz -- Mailing list info: https://lists.linux.it/listinfo/ltp