Received: by 2002:a05:7412:b10a:b0:f3:1519:9f41 with SMTP id az10csp247846rdb; Thu, 30 Nov 2023 04:01:07 -0800 (PST) X-Google-Smtp-Source: AGHT+IFOdvrkqi+TMUEZAtRPhhQGn9rVXBa0mADjiEaTnczteK//J3W78/MOOp43ipqDPYK4MC8l X-Received: by 2002:a05:6830:11cf:b0:6d6:4793:75ab with SMTP id v15-20020a05683011cf00b006d6479375abmr21422142otq.33.1701345667453; Thu, 30 Nov 2023 04:01:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701345667; cv=none; d=google.com; s=arc-20160816; b=ncRKPueqxhD7S2PCgNShozaNqUWeCK9gqUnjAN/7cO3xFVKkCGdzkI/D24OuuIQ7qr VLEJgiiJ3rx+t3ojMuwKQS0t9DkIC4dCvu9m6V/2/+BWLrkiu70Rwe67TjSoNEAe/ol+ ci+sPR2Q+fD+YRcnqbIuDxe8QgbIIiqL+qwPieHznc+7KFajVVbA2vmVpWj/z4Dyqoha CuZb+5aqqxKnhttwFimcajrkJ+61s7O60glaKoAUVo6ZsGUs0odJY2eZ0+jPorcUPvMe FPxo3C8NUxibMhltczg5oWLSG5/bSYg9+H6+HmDA2UoWsjatRZnfS2n8YR4Im7KOUOfN 1hFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:to:from:dkim-signature:dkim-signature :date; bh=ndX4No2pV02f83c7aScWg/bGo4s6E1w85WWMY13ARpA=; fh=H/sU1v7MV2DbPNIMZVLoCuKVif65LkZ2IGOBs8TI++g=; b=rStZlwf2f4UUc3gVmNPyKldambbfIxt6mN4xUaM28IzN2Ju4KsH7lwQfKWfGJm0jWB 1hz9Y5tGUFpxojDeviCU+1L38r2wYzfOFf2ZztIhVUXWobtTtagUQ3i9e0YgQTeAjIA4 wiCV4Il/T+enMbV9Xw2ylQG3f4SG97UU8VrUJBUQEpdLgPldOlQGaM4ob8sljTr456R1 GunxCBU1LFR8JI1mwuEcsMR9zWkOE7WhDiEyFlMTaFbew2iUtT/qmZ3+DxJGaB5Lp9u6 DaKfIDrWhtZpBtUDJTzZ4jOvEJPV1vcWpRLIF3k+FKOO8b9UO5rJ4F5GrcvCwf4oLZnX ge4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=URoou9yE; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from lipwig.vger.email (lipwig.vger.email. [23.128.96.33]) by mx.google.com with ESMTPS id m14-20020a9d6ace000000b006bc745960e0si354143otq.348.2023.11.30.04.01.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Nov 2023 04:01:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=URoou9yE; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id B7BAC8051BBE; Thu, 30 Nov 2023 04:01:01 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345246AbjK3MAp (ORCPT + 99 others); Thu, 30 Nov 2023 07:00:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345296AbjK3MAh (ORCPT ); Thu, 30 Nov 2023 07:00:37 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6939F10F1 for ; Thu, 30 Nov 2023 04:00:40 -0800 (PST) Date: Thu, 30 Nov 2023 13:00:36 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1701345637; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ndX4No2pV02f83c7aScWg/bGo4s6E1w85WWMY13ARpA=; b=URoou9yEZGAQw6bqSOt2qkQx0uyaxQu2+5W0DeaX3zbNm9eocIIucIu87W0dNHHaX13yMY WguGs9ZBhPc/91NCJpMM528MpyGsytqSGGmUW2TgurU7Cy0l7zfhWl9ovSHQ6JEBCetnss IhZbLp/EBcmEfvorSMWUstlwYSc2wCn/yYC77tGN7elAGfpg9LHonn0OaiQaGSnZoAg+vr X4MTnFZFb5/V+UOL/6OLVSot2oe0jZ6FgCI59uXZpWMiX/+bJPR3VJUL3YRTv19nMAiUt4 UcuiseMG91QsWomgZLn5GrR/SAOhI1vH+jdsUQ3kfkdv1GGujbHaNjyCi5S72Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1701345637; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ndX4No2pV02f83c7aScWg/bGo4s6E1w85WWMY13ARpA=; b=UhHN1nz0RRvJGJafkS+JOS5aTVVEq0tgGIliionbkTRj4ZxBIhJWvdW7jsTRsKnDPsPZwd Nm0CeVX7MfHbnBDA== From: Sebastian Andrzej Siewior To: rostedt@goodmis.org, tglx@linutronix.de, mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, vincent.guittot@linaro.org, linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com, bsegall@google.com, mgorman@suse.de, bristot@redhat.com, vschneid@redhat.com, zyhtheonly@gmail.com, zyhtheonly@yeah.net Subject: Re: [PATCH v2] sched/cputime: exclude ktimers threads in irqtime_account_irq Message-ID: <20231130120036.5EpZn4eo@linutronix.de> References: <20231127130754.3affb908@gandalf.local.home> <20231130094130.GA12116@didi-ThinkCentre-M930t-N000> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20231130094130.GA12116@didi-ThinkCentre-M930t-N000> X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Thu, 30 Nov 2023 04:01:02 -0800 (PST) On 2023-11-30 17:41:47 [+0800], tiozhang wrote: > In CONFIG_PREEMPT_RT kernel, ktimers also calls __do_softirq, > so when accounting CPUTIME_SOFTIRQ, ktimers need to be excluded > as well as ksoftirqd. > Also add this_cpu_ktimers to keep consistency with this_cpu_ksoftirqd. I'm still not sure what the benefit here is. It says align with ksoftirqd but why? Why don't we account softirq time for ksoftirqd (and should continue to do so for ktimersd)? ktimers runs almost all the time in softirq context. So does every force-threaded interrupt. Should we exclude them, too? Sebastian