Jaroslav Škarvada

@adriaan42 I like the 'offline' option more. It's more the TuneD way. It's also possible to explicitly define order of the instances by using the 'priority' option, otherwise it should...

Thanks for the report. Which versions? I am unable to reproduce with: python3-pyudev-0.21.0-11.fc31 dfuzzer-1.4-10.fc31.x86_64 ``` $ dfuzzer -v -n com.redhat.tuned -o /Tuned -i com.redhat.tuned.control -t switch_profile './dfuzzer.conf' file not found....

Checking against the latest git/master.

I tried with the 'balanced' profile, but maybe my machine is not fast enough to trigger the race.

I don't think it's required to call corresponding `remove_filter()` to every `filter_by()` call. From the pyudev documentation it seems the 'remove_filter' was added in the 0.15 version and `filter_by` call...

I checked the code, for the `filter_by` the pyudev calls `udev_monitor_filter_add_match_subsystem_devtype` and `udev_monitor_filter_update` with some minor glue logic. The systemd implements the `udev_monitor_filter_update` by the `setsockopt` call with the `SO_ATTACH_FILTER`,...

Please could you try replacing `self._udev_monitor.remove_filter()` with just small delay? To be sure that the problem is not caused by timing.

> I have several questions w.r.t. the scheduler plugin, which I examined in combination with the realtime profiles. I'm happy to contribute code if it turns out that things can...

@courtneypacheco please squash the commits to one. Use e.g. `git rebase -i` for it, then force push from the branch `git push -f`.

Tuned already reads udev events, so I think we could get the event. On my machine I am getting the following events: ``` KERNEL[5759.055142] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/PNP0C09:00/PNP0C0A:01/power_supply/BAT1 (power_supply) UDEV [5759.062214] change...