[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260108032328.85947-1-dongtai.guo@linux.dev>
Date: Thu, 8 Jan 2026 11:23:28 +0800
From: George Guo <dongtai.guo@...ux.dev>
To: etsal@...a.com
Cc: arighi@...dia.com,
changwoo@...lia.com,
dongtai.guo@...ux.dev,
guodongtai@...inos.cn,
linux-kernel@...r.kernel.org,
sched-ext@...ts.linux.dev,
tj@...nel.org,
void@...ifault.com
Subject: Re: [PATCH 1/1] sched_ext: Add error logging for dsq creation failures
Hi Etsal,
Thanks for reviewing!
> While the change looks correct, is there any benefit to it?
Yes, definitely. I found this issue while adding sched_ext support for
LoongArch. When scx_bpf_create_dsq() failed during my development, there
were no error messages at all, which made debugging difficult.
Specifically:
1. The failure was silent - no log, no error message in dmesg
2. I had to add bpf_printk() temporarily to confirm it was dsq creation failing
So the benefit is improved debuggability and faster issue diagnosis.
Thanks!
Powered by blists - more mailing lists