From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from m16.mail.163.com (m16.mail.163.com [220.197.31.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3661F2E2840 for ; Tue, 14 Jul 2026 09:49:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=220.197.31.5 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784022594; cv=none; b=UqZJwP/txcldY9qmtMRQZc3FuXB4UGmWgae2AiOlDngY0jb7Pus6dBhErfzCDYPzlPhsVxGDSUIQrz5VUp1DLNoJlgCVt8WP/8biajQLPoPe+hjjUqliEb11NZQCqcn7CKH/QeB01XCuj774YlFvy7bn5vCJXS3qSChdaNiaG3I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784022594; c=relaxed/simple; bh=Q/mMrctqR6EHEYYvO/03HiuQZkMqFGG0s0Lz4FfBTY8=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=HApfNp+FFgV+52OXSZeSwpC0TVe6C0C80Fzo+kloNC+1bqmEs4YsnA7iRhsa0ussv6s39dn138OdBNfhZ5FMN1Df6R9s6neBNyKFeLEHc2o/9oYvuvX4q/utCTobZmiJR2Aj9KlY7e9SytyD/6uEGHVEd6Os3KPvVyOa1emxHjM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=163.com; spf=pass smtp.mailfrom=163.com; dkim=pass (1024-bit key) header.d=163.com header.i=@163.com header.b=GxzlmZVg; arc=none smtp.client-ip=220.197.31.5 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=163.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=163.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=163.com header.i=@163.com header.b="GxzlmZVg" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Message-ID:Date:MIME-Version:Subject:To:From: Content-Type; bh=TfuOY7gn3K5d94a6Gv0suIkYgPbRQTb9zvtWBJ0LQ8U=; b=GxzlmZVgpQyXGrJMzy2WIAonxNMfERovbg+aNpdWLaIYgW6mg2oLliyN/nqAiv na40jKeQHd5BnZrh6wRvIkBmF2hM0f/WsvdwOTxMdo4OazYlIM+tN591WOhmt2q3 B0/pXLKQ22Uu8rWecHjK8El8nITo/2r2k5yhHWzRLzZs4= Received: from [10.42.12.206] (unknown []) by gzga-smtp-mtada-g0-4 (Coremail) with SMTP id _____wAnnhjtBVZqJI_pJg--.36799S2; Tue, 14 Jul 2026 17:48:30 +0800 (CST) Message-ID: Date: Tue, 14 Jul 2026 17:48:29 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] sched/core: Fix stale se.load when modifying nice value under sched_ext To: K Prateek Nayak , mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, vincent.guittot@linaro.org, tj@kernel.org Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de, vschneid@redhat.com, linux-kernel@vger.kernel.org, Wanwu Li References: <20260714091327.3-1-liwanwu9113@163.com> Content-Language: en-US From: liwanwu9113 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CM-TRANSID:_____wAnnhjtBVZqJI_pJg--.36799S2 X-Coremail-Antispam: 1Uf129KBjvJXoW7try5Jr4DJFyUAr4kJF1rtFb_yoW8Jw1kpF WkZFs3tFZrG3y09Fs2yw4fCryjg39IgF15Xw1a9a1qkr1YkFyYyF1xKw12kFW2gr10y3Wa qr1Y9as3ta43A3JanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07Uea0QUUUUU= X-CM-SenderInfo: polzt01zxziiqt6rljoofrz/xtbC2xCtNmpWBfB9jQAA3p Hello Prateek, Thank you for your reply and correction. I was not aware that this problem had already been addressed by another patch. I appreciate you taking the time to share this information. Please consider my patch withdrawn. Thank you again for your guidance. Best regards, Wanwu Li On 2026/7/14 17:30, K Prateek Nayak wrote: > Hello Wanwu, > > On 7/14/2026 2:43 PM, Wanwu Li wrote: >> [You don't often get email from liwanwu9113@163.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] >> >> From: Wanwu Li >> >> When a task's nice value is modified while running under sched_ext >> scheduling class, set_load_weight() calls reweight_task() which only >> updates static_prio but leaves p->se.load unchanged because sched_ext >> does not use it. After switching back to CFS, the stale se.load leads >> to incorrect load weight calculation. >> >> Fix this by explicitly refreshing p->se.load for sched_ext tasks after >> calling reweight_task(). >> >> Fixes: d32960528702 ("sched/fair: set_load_weight() must also call reweight_task() for SCHED_IDLE tasks") >> Signed-off-by: Wanwu Li > > Isn't this solved in > https://lore.kernel.org/lkml/20260528131238.3879110-1-quzicheng315@gmail.com/ >