Version 1.9 broke detection of tons of devices

[MinecraftNerrd1337]

EliteBook 840 G9 (i5 1235u). v1.8 finds 174 devices, v1.9 finds only 27, greatly limiting the possibilities for system interrupts tuning. I don't know if it would exhibit the same issue on all platforms but will be testing it and have a feeling it would.

[spddl]

Hi, this was discussed in Issue #7. It doesn't make sense to apply an interrupt policy to a device that doesn't support it. For this reason, only devices with IRQ lanes are now displayed.

[spddl]

I always find the UI/UX aspect a bit tricky. In the ContextMenu, you can now see the device tree, which includes all the devices listed underneath.

But I don't think that's very user-friendly.

GoInterruptPolicy.zip

[MinecraftNerrd1337]

@spddl Sorry for not answering, I've been (and am still kinda) busy asf. So I wasn't aware that devices without IRQ lanes didn't support setting driver affinity. Then this explains why some drivers like acpi.sys are very hard to move off CPU 0 (still haven't found good solution).
I will try the build you just sent me in the upcoming days (feel free to remind me if I forget).

[spddl]

No problem, this issue is public, so feedback from others who are interested is also very welcome. I think there are several valid approaches here.

[MinecraftNerrd1337]

@spddl If I understand it correctly, does this mean that driver files that aren't necessarily being called from an IRQ line cannot have affinity specified? My goal would mainly be to make sure at least core 1 and 0 are free of any interrupts above 1ms.