public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: vineethr@linux.ibm.com
Cc: bsegall@google.com, dietmar.eggemann@arm.com,
	gautham.shenoy@amd.com, juri.lelli@redhat.com,
	kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
	mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
	rostedt@goodmis.org, swapnil.sapkal@amd.com,
	vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH] sched/fair: Fix inaccurate h_nr_runnable accounting with delayed dequeue
Date: Mon, 20 Jan 2025 14:14:41 +0530	[thread overview]
Message-ID: <20250120084441.17746-1-vineethr@linux.ibm.com> (raw)
In-Reply-To: <20250120050639.48966-1-vineethr@linux.ibm.com>

> However, I was unable to trigger the WARN_ON by running hackbench in a
> cgroup without the patch. Could you please share the specific test
> scenario or configuration you used to reproduce it?

My mistake: SCHED_WARN_ON is a WARN_ONCE, so I had to clear it before
running hackbench to ensure the WARN_ON could be triggered again.

Now I am able to trigger the WARN_ON in the unpatched kernel while
running hackbench after executing `echo 1 > /sys/kernel/debug/clear_warn_once`
following the initial warning during the boot process. I have verified
that the patched kernel fixes the issue.

Thanks,
Madadi Vineeth Reddy

  reply	other threads:[~2025-01-20  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 10:58 [PATCH] sched/fair: Fix inaccurate h_nr_runnable accounting with delayed dequeue K Prateek Nayak
2025-01-17 13:25 ` Vincent Guittot
2025-01-17 15:59   ` K Prateek Nayak
2025-01-18  8:30     ` Vincent Guittot
2025-01-21  8:09       ` K Prateek Nayak
2025-01-21  9:53         ` Vincent Guittot
2025-01-20  5:06 ` Madadi Vineeth Reddy
2025-01-20  8:44   ` Madadi Vineeth Reddy [this message]
2025-01-20  9:14     ` K Prateek Nayak
2025-01-20  9:12   ` K Prateek Nayak
2025-01-21 12:21 ` [tip: sched/urgent] " tip-bot2 for K Prateek Nayak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250120084441.17746-1-vineethr@linux.ibm.com \
    --to=vineethr@linux.ibm.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gautham.shenoy@amd.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=swapnil.sapkal@amd.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox