ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<robclark> I suppose that is plausible
<steev> yeah, seems like it's heavy cpu usage that does it.... maybe some bad interaction with the new lmh driver?
<robclark> I mean, I'd expect normal userspace cpu busyness shouldn't delay irq's, but possibly lots of file I/O plus badly behaved other drivers could
FizzBuzz has joined #aarch64-laptops
<steev> hm, let me try something
<steev> # Compiler tasks
<steev> "^(make|cargo|rustc|rls|cicc|gcc|git)" = { priority = 20, policy = "idle" }
<steev> so that's in my process scheduler config
<steev> and if i disable it, it compiles without running into the enc issue
<steev> unless
<steev> i wonder if something is screwy in the scheduler
<steev> kernel side, i mean
<robclark> well, I mean, approximately 99.9% of the perf issues we've been dealing with are scheduler (or schedutil/boost, bit+little, etc) related.. but you'd still kinda hope that userspace threads (espc non-rt ones) aren't going to be blocking irqs
<robclark> *big+little
<steev> the big issue with when it happens is, there's no kinda recovery
<steev> reboot is the only way
<steev> oh! speaking of which
<steev> bamse: so, i made a change to my systemd config -
<steev> didn't mean to send so early
<steev> https://github.com/puavo-org/puavo-os/commit/240a73ebc99c1708a29eb66b988f60ec650f0a6d - changing the default timeout for apps to die from 90s to 8s seems to help a lot with rebooting - even rebooting via ssh
<steev> also... i've been trying out budgie desktop, and, i just don't get what is so awesome about it
<robclark> steev: yeah, maybe there is some edge case which things don't recover from gracefully.. you should probably ask abhinav (who seems not to be here but is on #freedreno), since the odds of me having a chance to dig into that are low
<steev> okay let me find the paste so i can pass it along and i'll do that
_ has joined #aarch64-laptops
FizzBuzz has quit [Ping timeout: 480 seconds]
_ has quit []
iivanov has joined #aarch64-laptops
norwoodites has joined #aarch64-laptops
pinskia has quit [Ping timeout: 480 seconds]
<macc24> is there a way to make linux kernel not use big cores at all if load is low enough?
<robclark> macc24: you can offline individual cores, or use thread affinity.. and possibly there are other ways
<HdkR> I guess they'd more want a scheduler that lets you very heavily weight processes towards the little cores until you change the policy from userspace?
<HdkR> weigh
<robclark> yeah, apparently with schedutil you can do that.. although I'm not really too familiar with the details.. I know there has been a lot of perf work on "trogdor" devices to tune that, but usually the problem is the opposite (things running on little cores when we want to get them onto big cores)
<HdkR> I currently have that problem on the HDK888 sadly
<robclark> (or maybe it is combination of schedutil and cgroups)
<macc24> hmm
norwoodites is now known as pinskia
gouchi has joined #aarch64-laptops
gouchi has quit [Remote host closed the connection]
iivanov has quit [Remote host closed the connection]
FizzBuzz has joined #aarch64-laptops