Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-12-04 Thread David Gibson
On Mon, Dec 04, 2017 at 09:32:00AM +0100, Cédric Le Goater wrote: > On 12/04/2017 02:59 AM, David Gibson wrote: > > On Fri, Dec 01, 2017 at 09:10:24AM +0100, Cédric Le Goater wrote: > >> On 12/01/2017 05:14 AM, David Gibson wrote: > >>> On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-12-04 Thread Cédric Le Goater
On 12/04/2017 02:59 AM, David Gibson wrote: > On Fri, Dec 01, 2017 at 09:10:24AM +0100, Cédric Le Goater wrote: >> On 12/01/2017 05:14 AM, David Gibson wrote: >>> On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wrote: On 11/30/2017 05:55 AM, David Gibson wrote: > On Thu, Nov

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-12-03 Thread David Gibson
On Fri, Dec 01, 2017 at 09:10:24AM +0100, Cédric Le Goater wrote: > On 12/01/2017 05:14 AM, David Gibson wrote: > > On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wrote: > >> On 11/30/2017 05:55 AM, David Gibson wrote: > >>> On Thu, Nov 23, 2017 at 02:29:47PM +0100, Cédric Le Goater

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-12-01 Thread Cédric Le Goater
On 12/01/2017 05:14 AM, David Gibson wrote: > On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wrote: >> On 11/30/2017 05:55 AM, David Gibson wrote: >>> On Thu, Nov 23, 2017 at 02:29:47PM +0100, Cédric Le Goater wrote: The XIVE object is designed to be always available, so it is

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-12-01 Thread David Gibson
On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wrote: > On 11/30/2017 05:55 AM, David Gibson wrote: > > On Thu, Nov 23, 2017 at 02:29:47PM +0100, Cédric Le Goater wrote: > >> The XIVE object is designed to be always available, so it is created > >> unconditionally on newer machines. >

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-12-01 Thread David Gibson
On Thu, Nov 30, 2017 at 03:38:46PM +, Cédric Le Goater wrote: > >> +} else { > >> +/* XIVE uses the full range of IRQ numbers. The CPU IPIs will > >> + * use the range below XICS_IRQ_BASE, which is unused by XICS. */ > >> +spapr->xive = spapr_xive_create(spapr,

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-11-30 Thread Cédric Le Goater
>> +} else { >> +/* XIVE uses the full range of IRQ numbers. The CPU IPIs will >> + * use the range below XICS_IRQ_BASE, which is unused by XICS. */ >> +spapr->xive = spapr_xive_create(spapr, XICS_IRQ_BASE + >> XICS_IRQS_SPAPR, >> +

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-11-30 Thread Cédric Le Goater
On 11/30/2017 05:55 AM, David Gibson wrote: > On Thu, Nov 23, 2017 at 02:29:47PM +0100, Cédric Le Goater wrote: >> The XIVE object is designed to be always available, so it is created >> unconditionally on newer machines. > > There doesn't actually seem to be anything dependent on machine >

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-11-30 Thread David Gibson
On Thu, Nov 23, 2017 at 02:29:47PM +0100, Cédric Le Goater wrote: > The XIVE object is designed to be always available, so it is created > unconditionally on newer machines. There doesn't actually seem to be anything dependent on machine version here. > Depending on the configuration and > the

[Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

2017-11-23 Thread Cédric Le Goater
The XIVE object is designed to be always available, so it is created unconditionally on newer machines. Depending on the configuration and the guest capabilities, the CAS negotiation process will decide which interrupt model to use, legacy or XIVE. The XIVE model makes use of the full range of