Re: [PATCH v4 07/19] spapr: Formalize notion of active interrupt controller

2019-10-09 Thread David Gibson
On Wed, Oct 09, 2019 at 11:19:26AM +0200, Cédric Le Goater wrote: > On 09/10/2019 08:08, David Gibson wrote: > > spapr now has the mechanism of constructing both XICS and XIVE instances of > > the SpaprInterruptController interface. However, only one of the interrupt > > controllers will actually

Re: [PATCH v4 07/19] spapr: Formalize notion of active interrupt controller

2019-10-09 Thread Cédric Le Goater
On 09/10/2019 08:08, David Gibson wrote: > spapr now has the mechanism of constructing both XICS and XIVE instances of > the SpaprInterruptController interface. However, only one of the interrupt > controllers will actually be active at any given time, depending on feature > negotiation with the g

Re: [PATCH v4 07/19] spapr: Formalize notion of active interrupt controller

2019-10-09 Thread Cédric Le Goater
On 09/10/2019 08:08, David Gibson wrote: > spapr now has the mechanism of constructing both XICS and XIVE instances of > the SpaprInterruptController interface. However, only one of the interrupt > controllers will actually be active at any given time, depending on feature > negotiation with the g

[PATCH v4 07/19] spapr: Formalize notion of active interrupt controller

2019-10-09 Thread David Gibson
spapr now has the mechanism of constructing both XICS and XIVE instances of the SpaprInterruptController interface. However, only one of the interrupt controllers will actually be active at any given time, depending on feature negotiation with the guest. This is handled in the current code via sp