[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260109103916.93454-1-dongtai.guo@linux.dev>
Date: Fri, 9 Jan 2026 18:39:16 +0800
From: George Guo <dongtai.guo@...ux.dev>
To: arighi@...dia.com
Cc: changwoo@...lia.com,
dongtai.guo@...ux.dev,
etsal@...a.com,
guodongtai@...inos.cn,
linux-kernel@...r.kernel.org,
sched-ext@...ts.linux.dev,
tj@...nel.org,
void@...ifault.com
Subject: Re: [PATCH v2 1/1] sched_ext: Add error logging for dsq creation failures
> Huh? No, we already get an error message both in dmesg and in stdout when
> scx_bpf_create_dsq() fails, so I don't think this is required.
>
> Are you sure you were not hitting other issues when your scheduler failed
> to load silently?
Hi Andrea,
Here take an instance.
You need add bpf_printk in BPF_STRUCT_OPS_SLEEPABLE(central_init),
even with dmesg when central_init fails, as central_init have multiply
error return.
Thanks!
Powered by blists - more mailing lists