On 09/28/2017 12:03 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2017-09-28 at 10:51 +0200, Cédric Le Goater wrote:
>> probably, I just removed the properties under QEMU and could
>> boot the guest, with disks and network.
>
> As long as you don't use LSIs...
That I didn't test much. Which the de
On Thu, 2017-09-28 at 10:51 +0200, Cédric Le Goater wrote:
> probably, I just removed the properties under QEMU and could
> boot the guest, with disks and network.
As long as you don't use LSIs...
>
> > Do you have a DT snapshot from pHyp for me to look at ?
>
>
> # lsprop /proc/device-tree/i
On Thu, 2017-09-21 at 11:35 +1000, David Gibson wrote:
> > >> +_FDT(fdt_setprop_string(fdt, node, "device_type", "power-ivpe"));
> > >> +_FDT(fdt_setprop(fdt, node, "reg", timas, sizeof(timas)));
> > >> +
> > >> +_FDT(fdt_setprop_string(fdt, node, "compatible", "ibm,power-ivpe"));
> > >
On 09/28/2017 10:43 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2017-09-21 at 13:21 +0200, Cédric Le Goater wrote:
>> Let me be more precise. I am saying that the interrupt-controller
>> and #interrupt-cells properties are not needed under the main interrupt
>> controller node. They can be remove
On Thu, 2017-09-21 at 13:21 +0200, Cédric Le Goater wrote:
> Let me be more precise. I am saying that the interrupt-controller
> and #interrupt-cells properties are not needed under the main interrupt
> controller node. They can be removed from the tree and the Linux guest
> kernel will boot per
On Thu, Sep 21, 2017 at 01:21:10PM +0200, Cédric Le Goater wrote:
> On 09/21/2017 03:35 AM, David Gibson wrote:
> > On Wed, Sep 20, 2017 at 02:26:32PM +0200, Cédric Le Goater wrote:
> >> On 09/19/2017 10:44 AM, David Gibson wrote:
> >>> On Mon, Sep 11, 2017 at 07:12:32PM +0200, Cédric Le Goater wro
On 09/21/2017 03:35 AM, David Gibson wrote:
> On Wed, Sep 20, 2017 at 02:26:32PM +0200, Cédric Le Goater wrote:
>> On 09/19/2017 10:44 AM, David Gibson wrote:
>>> On Mon, Sep 11, 2017 at 07:12:32PM +0200, Cédric Le Goater wrote:
Like for XICS, the XIVE interface for the guest is described in t
On Wed, Sep 20, 2017 at 02:26:32PM +0200, Cédric Le Goater wrote:
> On 09/19/2017 10:44 AM, David Gibson wrote:
> > On Mon, Sep 11, 2017 at 07:12:32PM +0200, Cédric Le Goater wrote:
> >> Like for XICS, the XIVE interface for the guest is described in the
> >> device tree under the "interrupt-contro
On 09/19/2017 10:44 AM, David Gibson wrote:
> On Mon, Sep 11, 2017 at 07:12:32PM +0200, Cédric Le Goater wrote:
>> Like for XICS, the XIVE interface for the guest is described in the
>> device tree under the "interrupt-controller" node. A couple of new
>> properties are specific to XIVE :
>>
>> -
On Mon, Sep 11, 2017 at 07:12:32PM +0200, Cédric Le Goater wrote:
> Like for XICS, the XIVE interface for the guest is described in the
> device tree under the "interrupt-controller" node. A couple of new
> properties are specific to XIVE :
>
> - "reg"
>
>contains the base address and size o
Like for XICS, the XIVE interface for the guest is described in the
device tree under the "interrupt-controller" node. A couple of new
properties are specific to XIVE :
- "reg"
contains the base address and size of the thread interrupt
managnement areas (TIMA), also called rings, for the U
11 matches
Mail list logo
