ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
cengiz_io has joined #armlinux
apritzel has quit [Ping timeout: 268 seconds]
shawnguo has joined #armlinux
LeSpocky_ has joined #armlinux
LeSpocky has quit [Ping timeout: 248 seconds]
amitk has joined #armlinux
kristina1 has joined #armlinux
tmlind_ has joined #armlinux
tmlind has quit [*.net *.split]
benh has quit [*.net *.split]
kristinam has quit [*.net *.split]
eballetbo has quit [*.net *.split]
eballetbo has joined #armlinux
benh has joined #armlinux
gclement_ has quit [*.net *.split]
pg12_ has quit [*.net *.split]
biot has quit [*.net *.split]
netonaut has quit [*.net *.split]
krzk has quit [*.net *.split]
j`ey has quit [*.net *.split]
biot_ has joined #armlinux
krzk_ has joined #armlinux
gclement has joined #armlinux
j`ey_ has joined #armlinux
netonaut_ has joined #armlinux
pg12_ has joined #armlinux
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #armlinux
Drek45 has joined #armlinux
apritzel has joined #armlinux
iivanov has joined #armlinux
frieder has joined #armlinux
LeSpocky_ is now known as LeSpocky
apritzel has quit [Ping timeout: 240 seconds]
tudorel has joined #armlinux
tre has joined #armlinux
Pali has joined #armlinux
Drek45 has quit [Remote host closed the connection]
j`ey_ is now known as j`ey
<maz>
marex: you sure can put traces in the scheduler, but that will impact latency.
<maz>
marex: schedule() not returning before a whole second probably means the CPU is busy running other tasks, and only schedules you back when convenient.
<maz>
marex: but it also could be that you are loosing timer interrupts (urgh.....) and that leads to the scheduler going bonkers.
nsaenz has joined #armlinux
<LeSpocky>
hello
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
biot_ has quit [Quit: Reconnecting]
biot has joined #armlinux
djrscally has joined #armlinux
apritzel has joined #armlinux
alpernebbi has joined #armlinux
amitk_ has joined #armlinux
amitk has quit [Ping timeout: 248 seconds]
<marex>
maz: well, I also patched the gic driver, I am getting timer interrupts on all cores, all but the core running the xiic interrupt also call schedule() every time quantum or so, the core which ran the xiic interrupt thread exits that thread, calls schedule, and starts running some kworker thread which runs there for a second or so
valsch has joined #armlinux
j`ey has quit [Quit: leaving]
j_ey has joined #armlinux
alpernebbi has quit [Quit: alpernebbi]
rperier has joined #armlinux
rperier has quit [Client Quit]
rperier has joined #armlinux
torez has joined #armlinux
Drek45 has joined #armlinux
frieder has quit [Remote host closed the connection]
headless has joined #armlinux
jlinton has quit [Quit: Client closed]
headless_ has joined #armlinux
headless has quit [Ping timeout: 250 seconds]
headless_ is now known as headless
tre has quit [Remote host closed the connection]
j_ey is now known as j`ey
russ has quit [Ping timeout: 258 seconds]
gcl has joined #armlinux
tudorel has quit [Quit: tudorel]
russ has joined #armlinux
amitk has joined #armlinux
amitk_ has quit [Ping timeout: 252 seconds]
amitk_ has joined #armlinux
amitk has quit [Ping timeout: 250 seconds]
russ has quit [Ping timeout: 250 seconds]
amitk has joined #armlinux
amitk_ has quit [Ping timeout: 250 seconds]
<marex>
maz: well ... the interrupt kernel thread got scheduled at 1.2 seconds mark ...
<marex>
that is insane
<marex>
but at least now I know what is going on
amitk has quit [Ping timeout: 240 seconds]
amitk has joined #armlinux
amitk has quit [Ping timeout: 240 seconds]
amitk has joined #armlinux
amitk has quit [Ping timeout: 240 seconds]
jbru has quit [Ping timeout: 240 seconds]
headless has quit [Quit: Konversation terminated!]