Consider moving away the f/w checking code out from the qubes-manager...

[marmarek]

Reported by joanna on 2 Apr 2011 14:34 UTC
...and perhaps rewrite it in C -- it really eats lots of CPU, and is currently executed every 5 sec -- this is quite a killer for batteries I think. Also, I think such code should be independent from the manager and should be part of the core instead.

Migrated-From: https://wiki.qubes-os.org/ticket/182

[marmarek]

Modified by joanna on 6 Apr 2011 12:37 UTC

[marmarek]

Modified by joanna on 6 Apr 2011 12:37 UTC

[marmarek]

Comment by marmarek on 23 May 2011 16:31 UTC
Perhaps the better idea is just to display message directly from firewallvm, when loading firewall failed.
Maybe left only some flag in xenstore indicating result of last firewall loading (success/fail).

This will eliminate one data flow VM->dom0 which is always good.

[marmarek]

Comment by marmarek on 23 May 2011 16:31 UTC
Perhaps the better idea is just to display message directly from firewallvm, when loading firewall failed.
Maybe left only some flag in xenstore indicating result of last firewall loading (success/fail).

This will eliminate one data flow VM->dom0 which is always good.

[marmarek]

Comment by marmarek on 10 Jun 2011 16:49 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=48d520f8475ed4b3ac11380595c3daf56a39e5ca

[marmarek]

Comment by marmarek on 10 Jun 2011 16:49 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=48d520f8475ed4b3ac11380595c3daf56a39e5ca