On 12/02/2017 03:48 PM, Benjamin Herrenschmidt wrote:
> On Sat, 2017-12-02 at 15:38 +0100, Cédric Le Goater wrote:
>> Hmm, yes. So, the current design for sPAPR handles all sources
>> under the same XIVE object with a global memory region for all
>> the ESBs.
>>
>> The first RFC had a mechanism
On Sat, 2017-12-02 at 15:38 +0100, Cédric Le Goater wrote:
> Hmm, yes. So, the current design for sPAPR handles all sources
> under the same XIVE object with a global memory region for all
> the ESBs.
>
> The first RFC had a mechanism to register source objects into
> the XIVE main one,
On 12/02/2017 03:24 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2017-11-28 at 17:40 +1100, David Gibson wrote:
>>> @@ -368,6 +368,10 @@ static void spapr_xive_realize(DeviceState *dev, Error
>>> **errp)
>>> /* Allocate the IVT (Interrupt Virtualization Table) */
>>> xive->ivt =
On Tue, 2017-11-28 at 17:40 +1100, David Gibson wrote:
> > @@ -368,6 +368,10 @@ static void spapr_xive_realize(DeviceState *dev, Error
> > **errp)
> > /* Allocate the IVT (Interrupt Virtualization Table) */
> > xive->ivt = g_malloc0(xive->nr_irqs * sizeof(XiveIVE));
> >
> > +/*
On 11/28/2017 06:40 AM, David Gibson wrote:
> On Thu, Nov 23, 2017 at 02:29:41PM +0100, Cédric Le Goater wrote:
>> The XIVE interrupt sources can have different characteristics depending
>> on their nature and the HW level in use. The sPAPR specs provide a set of
>> flags to describe them :
>>
>>
On Thu, Nov 23, 2017 at 02:29:41PM +0100, Cédric Le Goater wrote:
> The XIVE interrupt sources can have different characteristics depending
> on their nature and the HW level in use. The sPAPR specs provide a set of
> flags to describe them :
>
> - XIVE_SRC_H_INT_ESB the Event State Buffers are
The XIVE interrupt sources can have different characteristics depending
on their nature and the HW level in use. The sPAPR specs provide a set of
flags to describe them :
- XIVE_SRC_H_INT_ESB the Event State Buffers are controlled with a
specific hcall H_INT_ESB and not
