On Tue, Sep 11, 2018 at 09:56:06AM +0200, Cédric Le Goater wrote:
> On 09/11/2018 09:34 AM, Greg Kurz wrote:
> > On Tue, 11 Sep 2018 07:55:02 +0200
> > Cédric Le Goater wrote:
> >
> >> The number of MSI interrupts a sPAPR machine can allocate is in direct
> >> relation with the number of interrup
On Tue, Sep 11, 2018 at 07:55:02AM +0200, Cédric Le Goater wrote:
> The number of MSI interrupts a sPAPR machine can allocate is in direct
> relation with the number of interrupts of the sPAPRIrq backend. Define
> statically this value at the sPAPRIrq class level and use it for the
> "ibm,pe-total-
On 09/11/2018 09:34 AM, Greg Kurz wrote:
> On Tue, 11 Sep 2018 07:55:02 +0200
> Cédric Le Goater wrote:
>
>> The number of MSI interrupts a sPAPR machine can allocate is in direct
>> relation with the number of interrupts of the sPAPRIrq backend. Define
>> statically this value at the sPAPRIrq cl
On Tue, 11 Sep 2018 07:55:02 +0200
Cédric Le Goater wrote:
> The number of MSI interrupts a sPAPR machine can allocate is in direct
> relation with the number of interrupts of the sPAPRIrq backend. Define
> statically this value at the sPAPRIrq class level and use it for the
> "ibm,pe-total-#msi"
The number of MSI interrupts a sPAPR machine can allocate is in direct
relation with the number of interrupts of the sPAPRIrq backend. Define
statically this value at the sPAPRIrq class level and use it for the
"ibm,pe-total-#msi" property of the sPAPR PHB.
According to the PAPR specs, "ibm,pe-tot
