Re: [PATCH] node_device: Do not lock the driver state needlessly

2025-02-12 Thread Ján Tomko
On a Wednesday in 2025, Martin Kletzander wrote: On Fri, Feb 07, 2025 at 04:32:07PM +0100, Ján Tomko wrote: On a Friday in 2025, Martin Kletzander wrote: When processing the PCI devices we can only read the configs for each of them if running as privileged. That information is saved in the dri

Re: [PATCH] node_device: Do not lock the driver state needlessly

2025-02-12 Thread Martin Kletzander
On Fri, Feb 07, 2025 at 04:32:07PM +0100, Ján Tomko wrote: On a Friday in 2025, Martin Kletzander wrote: When processing the PCI devices we can only read the configs for each of them if running as privileged. That information is saved in the driver state as a boolean introduced in commit 643c74

Re: [PATCH] node_device: Do not lock the driver state needlessly

2025-02-07 Thread Ján Tomko
On a Friday in 2025, Martin Kletzander wrote: When processing the PCI devices we can only read the configs for each of them if running as privileged. That information is saved in the driver state as a boolean introduced in commit 643c74abff01. However since Please don't put a period right aft

[PATCH] node_device: Do not lock the driver state needlessly

2025-02-07 Thread Martin Kletzander
When processing the PCI devices we can only read the configs for each of them if running as privileged. That information is saved in the driver state as a boolean introduced in commit 643c74abff01. However since that version it is only written to once during nodeStateInitialize() and only read fr