Re: [PATCH v2 2/6] tools/oxenstored: Bind the DOM_EXC VIRQ in in Event.init()

> On 30 Nov 2022, at 16:54, Andrew Cooper wrote: > > Xenstored always needs to bind the DOM_EXC VIRQ. > > Instead of doing it shortly after the call to Event.init(), do it in the > init() call itself. This removes the need for the field to be a mutable > option. > > It will also simplify a

Re: [PATCH v2 2/6] tools/oxenstored: Bind the DOM_EXC VIRQ in in Event.init()

> On 30 Nov 2022, at 16:54, Andrew Cooper wrote: > > Xenstored always needs to bind the DOM_EXC VIRQ. > > Instead of doing it shortly after the call to Event.init(), do it in the > init() call itself. This removes the need for the field to be a mutable > option. > > It will also simplify a

[PATCH v2 2/6] tools/oxenstored: Bind the DOM_EXC VIRQ in in Event.init()

Xenstored always needs to bind the DOM_EXC VIRQ. Instead of doing it shortly after the call to Event.init(), do it in the init() call itself. This removes the need for the field to be a mutable option. It will also simplify a future change to restore both parts from the live update record,