Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp655330imw; Fri, 15 Jul 2022 10:17:59 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tx3hsBFi+5R9AuayoIZ30papFdbgv3OxfzvLLd6IVGo5H8EokZI2FO30cOEMj9OksPf8R8 X-Received: by 2002:a63:d350:0:b0:416:15ec:3d36 with SMTP id u16-20020a63d350000000b0041615ec3d36mr13620174pgi.37.1657905479224; Fri, 15 Jul 2022 10:17:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657905479; cv=none; d=google.com; s=arc-20160816; b=W6VsJwiTxE9Xh8z0Q6AAOoDETZ8EVKRoUz0Ly716XzRs/CRURUjKsdE7ZgoS1dp/6l iCeWow5WftLlrqFAL0ypT2G31qZb8+fkah5eStx62PEYt5dgCivIZRFD//RnJDtOncZ6 fUxyMiSZpj86ARVG3MsSvhbQtouASU/O7w7WbH7okgl+fdo8K3S1+P9F8MduI2AqarW+ 839Hq4CGUG6fz8B/q4DpcH6EJMC0X0W17JYdEEc8T/rv5AH7wui4rMcRMXJbNhjCBoKS HxCmr8L1urtyjp4zIEvo3GJQ7/hRPDkKaYXWL1gENJDVbmy6FRPrT8zEvjWuwEbFfIHQ 4aBA== 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:cc:to:from:date:dkim-signature; bh=f68FcbXZ0g9TjJ9n4Wp7AGTeKBQTeaGnrFF7gAH+ZUo=; b=UHFQGZGlweGO/mRRq6S/iEFQr1RPLRCG5Kf+TzJoNfQqIVPaqwcS2qhh+wzaVNzxGd RG1xEIn4id8J0jeScUZV6rFkuS+YqmSi4HIBdG4ivTrNAB3YOLVIv1goy3UJPjV20+wf +6ZtTrE8Wu4PtfSV1a4dHqorrmvtSn8eaO4iUWgHmYPvleSoNyb4rwjbu5D0szbo2ZCu FYNHZMHkaj9dLhSZo2i0m70ZKHfnuPakCuo6j0CCnsVMG4MdQyo+7WOg1AElXZ22Cq05 9GM7Je8BrU01wGYxCCt6Ew6xPUDVH33oulM/NBACed/othnDq+Kl0RPSeJziqLd5VbTn whpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UN1kTJQI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k14-20020a634b4e000000b004120f7d1e4csi89250pgl.611.2022.07.15.10.17.43; Fri, 15 Jul 2022 10:17:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UN1kTJQI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234478AbiGOQyh (ORCPT + 99 others); Fri, 15 Jul 2022 12:54:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38492 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234399AbiGOQyf (ORCPT ); Fri, 15 Jul 2022 12:54:35 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 35FFF7A519 for ; Fri, 15 Jul 2022 09:54:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657904072; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=f68FcbXZ0g9TjJ9n4Wp7AGTeKBQTeaGnrFF7gAH+ZUo=; b=UN1kTJQImmTv/VZcq+GPKa16LLV5vtSDYEtvmhFyo23pC2XhYu/wca/Indbe7Tu0fLOOLd UqslLEbvB82xrvcqsy2Lzy5MUasefeRf+QBoYI6xyZQH6T4ptp6S1tTEINxgU/cnjU/urL uNWnjH8FbxOAzECgyFLp1YakwNkD/KM= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-365-gbneN4JdPU6RSbPPbDMYbQ-1; Fri, 15 Jul 2022 12:54:31 -0400 X-MC-Unique: gbneN4JdPU6RSbPPbDMYbQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B25F9811E7A; Fri, 15 Jul 2022 16:54:30 +0000 (UTC) Received: from lorien.usersys.redhat.com (unknown [10.39.193.130]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 63409C28118; Fri, 15 Jul 2022 16:54:25 +0000 (UTC) Date: Fri, 15 Jul 2022 12:54:21 -0400 From: Phil Auld To: Nicolas Saenz Julienne Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com, bristot@redhat.com, vschneid@redhat.com, cmetcalf@ezchip.com, mgorman@suse.de, bsegall@google.com, rostedt@goodmis.org, dietmar.eggemann@arm.com, vincent.guittot@linaro.org, juri.lelli@redhat.com, peterz@infradead.org, mingo@redhat.com, mtosatti@redhat.com Subject: Re: [PATCH] nohz/full, sched/rt: Fix missed tick-reenabling bug in dequeue_task_rt Message-ID: References: <20220628092259.330171-1-nsaenzju@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220628092259.330171-1-nsaenzju@redhat.com> X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 28, 2022 at 11:22:59AM +0200 Nicolas Saenz Julienne wrote: > dequeue_task_rt() only decrements 'rt_rq->rt_nr_running' after having > called sched_update_tick_dependency() preventing it from re-enabling the > tick on systems that no longer have pending SCHED_RT tasks but have > multiple runnable SCHED_OTHER tasks: > > dequeue_task_rt() > dequeue_rt_entity() > dequeue_rt_stack() > dequeue_top_rt_rq() > sub_nr_running() // decrements rq->nr_running > sched_update_tick_dependency() > sched_can_stop_tick() // checks rq->rt.rt_nr_running, > ... > __dequeue_rt_entity() > dec_rt_tasks() // decrements rq->rt.rt_nr_running > ... > > Every other scheduler class performs the operation in the opposite > order, and sched_update_tick_dependency() expects the values to be > updated as such. So avoid the misbehaviour by inverting the order in > which the above operations are performed in the RT scheduler. > > Fixes: 76d92ac305f2 ("sched: Migrate sched to use new tick dependency mask model") > Signed-off-by: Nicolas Saenz Julienne That's been around for a while. This change looks right and makes sense to me. Thanks, Phil Reviewed-by: Phil Auld --