All of lore.kernel.org
 help / color / mirror / Atom feed
* [TESTDAY] Test report
@ 2016-05-13 20:34 Edgar E. Iglesias
  2016-05-14 18:15 ` Julien Grall
  0 siblings, 1 reply; 28+ messages in thread
From: Edgar E. Iglesias @ 2016-05-13 20:34 UTC (permalink / raw)
  To: Xen-devel; +Cc: Julien Grall, Stefano Stabellini

* Hardware: ZCU102 ZynqMP board
* Software: Rolled my own dom0 linux
* Tested: Start dom0

The test fails with the following error:
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 0000000000080000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000040000000 (512MB)
(XEN) Grant table range: 0x0000007fe00000-0x0000007fe5f000
(XEN) smmu: /amba/smmu@fd800000: d0: p2maddr 0x000000007ff64000
(XEN) Device tree generation failed (-22).

It's the PCIe node that is causing trouble, the bindings are here:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pci/xilinx-nwl-pcie.txt

It's that inner interrupt-controller node that is causing problems as
Xen/ARM only supports one interrupt-controller node (IIUC).

Disabling the pcie node for zynqmp boards gets dom0 to boot (obviously
without PCIe support).

Does it make sense to try to fix this problem this late inte the
release cycle? (I can have a closer look and propose a possible fix
for discussion)

Or should we disable the PCIe for ZynqMP for now and try to fix this
properly for 4.8?

Any ideas/suggestions?

Best regards,
Edgar

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2016-05-13 20:34 [TESTDAY] Test report Edgar E. Iglesias
@ 2016-05-14 18:15 ` Julien Grall
  2016-05-14 19:04   ` Edgar E. Iglesias
  0 siblings, 1 reply; 28+ messages in thread
From: Julien Grall @ 2016-05-14 18:15 UTC (permalink / raw)
  To: Edgar E. Iglesias, Xen-devel; +Cc: Stefano Stabellini, Wei Liu

Hello Edgar,

Thank you for the testing.

On 13/05/2016 21:34, Edgar E. Iglesias wrote:
> * Hardware: ZCU102 ZynqMP board
> * Software: Rolled my own dom0 linux
> * Tested: Start dom0
>
> The test fails with the following error:
> (XEN) I/O virtualisation enabled
> (XEN)  - Dom0 mode: Relaxed
> (XEN) Interrupt remapping enabled
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading kernel from boot module @ 0000000000080000
> (XEN) Allocating 1:1 mappings totalling 512MB for dom0:
> (XEN) BANK[0] 0x00000020000000-0x00000040000000 (512MB)
> (XEN) Grant table range: 0x0000007fe00000-0x0000007fe5f000
> (XEN) smmu: /amba/smmu@fd800000: d0: p2maddr 0x000000007ff64000
> (XEN) Device tree generation failed (-22).


You could uncomment //#define DEBUG_DT in domain_build.c, rebuild and 
paste the log here?

>
> It's the PCIe node that is causing trouble, the bindings are here:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pci/xilinx-nwl-pcie.txt
>
> It's that inner interrupt-controller node that is causing problems as
> Xen/ARM only supports one interrupt-controller node (IIUC).

It should not matter, unless the interrupt controller is used to 
describe some interrupts in device-tree.

Is this node used later in the DT?

>
> Disabling the pcie node for zynqmp boards gets dom0 to boot (obviously
> without PCIe support).
>
> Does it make sense to try to fix this problem this late inte the
> release cycle? (I can have a closer look and propose a possible fix
> for discussion)

I would try to fix it in Xen 4.7 if the patch is simple. Otherwise we 
could backport it after the release.

>
> Or should we disable the PCIe for ZynqMP for now and try to fix this
> properly for 4.8?

Was PCIe working on Xen 4.6? If yes, it's the regression and we could 
consider it as a blocker for the release (CC Wei for that).

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2016-05-14 18:15 ` Julien Grall
@ 2016-05-14 19:04   ` Edgar E. Iglesias
  2016-05-16  9:58     ` Wei Liu
  2016-05-16 13:20     ` Julien Grall
  0 siblings, 2 replies; 28+ messages in thread
From: Edgar E. Iglesias @ 2016-05-14 19:04 UTC (permalink / raw)
  To: Julien Grall; +Cc: Stefano Stabellini, Wei Liu, Xen-devel

On Sat, May 14, 2016 at 07:15:55PM +0100, Julien Grall wrote:
> Hello Edgar,
> 
> Thank you for the testing.
> 
> On 13/05/2016 21:34, Edgar E. Iglesias wrote:
> >* Hardware: ZCU102 ZynqMP board
> >* Software: Rolled my own dom0 linux
> >* Tested: Start dom0
> >
> >The test fails with the following error:
> >(XEN) I/O virtualisation enabled
> >(XEN)  - Dom0 mode: Relaxed
> >(XEN) Interrupt remapping enabled
> >(XEN) *** LOADING DOMAIN 0 ***
> >(XEN) Loading kernel from boot module @ 0000000000080000
> >(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
> >(XEN) BANK[0] 0x00000020000000-0x00000040000000 (512MB)
> >(XEN) Grant table range: 0x0000007fe00000-0x0000007fe5f000
> >(XEN) smmu: /amba/smmu@fd800000: d0: p2maddr 0x000000007ff64000
> >(XEN) Device tree generation failed (-22).
> 
> 
> You could uncomment //#define DEBUG_DT in domain_build.c, rebuild and paste
> the log here?

Yes, I've pasted it to the end of the email.

> 
> >
> >It's the PCIe node that is causing trouble, the bindings are here:
> >http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pci/xilinx-nwl-pcie.txt
> >
> >It's that inner interrupt-controller node that is causing problems as
> >Xen/ARM only supports one interrupt-controller node (IIUC).
> 
> It should not matter, unless the interrupt controller is used to describe
> some interrupts in device-tree.
> 
> Is this node used later in the DT?

Actually it is only used from the PCIe node itself. Pasting the device tree node:

                pcie: pcie@fd0e0000 {
                        compatible = "xlnx,nwl-pcie-2.11";
                        status = "disabled";
                        #address-cells = <3>;
                        #size-cells = <2>;
                        #interrupt-cells = <1>;
                        device_type = "pci";
                        interrupt-parent = <&gic>;
                        interrupts = <0 118 4>,
                                     <0 116 4>,
                                     <0 115 4>, /* MSI_1 [63...32] */
                                     <0 114 4>; /* MSI_0 [31...0] */
                        interrupt-names = "misc", "intx", "msi_1", "msi_0";
                        reg = <0x0 0xfd0e0000 0x0 0x1000>,
                              <0x0 0xfd480000 0x0 0x1000>,
                              <0x0 0xe0000000 0x0 0x1000000>;
                        reg-names = "breg", "pcireg", "cfg";
                        ranges = <0x02000000 0x00000000 0xe1000000 0x00000000 0xe1000000 0 0x0f000000>;
                        interrupt-map-mask = <0x0 0x0 0x0 0x7>;
                        interrupt-map = <0x0 0x0 0x0 0x1 &pcie_intc 0x1>,
                                        <0x0 0x0 0x0 0x2 &pcie_intc 0x2>,
                                        <0x0 0x0 0x0 0x3 &pcie_intc 0x3>,
                                        <0x0 0x0 0x0 0x4 &pcie_intc 0x4>;
                        pcie_intc: legacy-interrupt-controller {
                                interrupt-controller;
                                #address-cells = <0>;
                                #interrupt-cells = <1>;
                        };
                };


You can see that it is used in the interrupt-map properties.
IIUC, the interrupt lines connected to the pcie_intc controller
are simply going to be combined into the "intx" line IRQ 116 on
going from the pcie bridge towards the gic.

I don't think we need to do much than to ignore the node but what
we present to dom0 must look the same..

> 
> >
> >Disabling the pcie node for zynqmp boards gets dom0 to boot (obviously
> >without PCIe support).
> >
> >Does it make sense to try to fix this problem this late inte the
> >release cycle? (I can have a closer look and propose a possible fix
> >for discussion)
> 
> I would try to fix it in Xen 4.7 if the patch is simple. Otherwise we could
> backport it after the release.

OK, great.
I'll have a closer look too then.

I was trying this, but it may be too permissive:

diff --git a/xen/common/device_tree.c b/xen/common/device_tree.c
index 0ed86a7..68cb162 100644
--- a/xen/common/device_tree.c
+++ b/xen/common/device_tree.c
@@ -1176,6 +1176,15 @@ int dt_for_each_irq_map(const struct dt_device_node *dev,
         for ( i = 0; i < pintsize; i++ )
             dt_raw_irq.specifier[i] = dt_read_number(imap + i, 1);
 
+        if (dt_raw_irq.controller != dt_interrupt_controller) {
+            /* If this is not the main interrupt controller, we assume
+             * it's part of a bus-bridge and ignore remapping IRQs for it.
+             * Xen only supports one interrupt controller at the moment.  */
+            imap += pintsize;
+            imaplen -= pintsize;
+            continue;
+        }


> 
> >
> >Or should we disable the PCIe for ZynqMP for now and try to fix this
> >properly for 4.8?
> 
> Was PCIe working on Xen 4.6? If yes, it's the regression and we could
> consider it as a blocker for the release (CC Wei for that).

No, these PCIe nodes were added recently.
The device tree bindings were different before but after discussing
with the upstream Linux folks they got changed.

Thanks and Best regards,
Edgar


Log:


\rdone
\rBytes transferred = 47624312 (2d6b078 hex)
\rUsing ethernet@ff0e0000 device
\rTFTP from server 192.168.10.1; our IP address is 192.168.10.28
\rFilename 'xen.ub'.
\rLoad address: 0x8000000
\rLoading: *\b#################################################################
\r	 #################################################################
\r	 ########################
\r	 5.8 MiB/s
\rdone
\rBytes transferred = 788064 (c0660 hex)
\r## Booting kernel from Legacy Image at 08000000 ...
\r   Image Name:   
\r   Image Type:   AArch64 Linux Kernel Image (uncompressed)
\r   Data Size:    788000 Bytes = 769.5 KiB
\r   Load Address: 05000000
\r   Entry Point:  05000000
\r   Verifying Checksum ... OK
\r## Flattened Device Tree blob at 06000000
\r   Booting using the fdt blob at 0x6000000
\r   Loading Kernel Image ... OK
\r   Loading Device Tree to 0000000007ff6000, end 0000000007fff799 ... OK

\rStarting kernel ...

\r- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000000000000 - 000000007fffffff
(XEN) 
(XEN) MODULE[0]: 0000000007ff6000 - 0000000007ffd000 Device Tree  
(XEN) MODULE[1]: 0000000000080000 - 0000000004080000 Kernel       
(XEN)  RESVD[0]: 0000000007ff6000 - 0000000007ffd000
(XEN) 
(XEN) Command line: console=dtuart dtuart=serial0 dom0_mem=512M bootscrub=0 timer_slop=0
(XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
(XEN) Update BOOTMOD_XEN from 0000000005000000-000000000510ce01 => 000000007fe00000-000000007ff0ce01
(XEN) Domain heap initialised
(XEN)  -> unflatten_device_tree()
(XEN) Unflattening device tree:
(XEN) magic: 0xd00dfeed
(XEN) size: 0x007000
(XEN) version: 0x000011
(XEN)   size is 0x12618 allocating...
(XEN)   unflattening 80007ff20000...
(XEN) fixed up name for  -> 
(XEN) fixed up name for cpus -> cpus
(XEN) fixed up name for cpu@0 -> cpu
(XEN) fixed up name for cpu@1 -> cpu
(XEN) fixed up name for cpu@2 -> cpu
(XEN) fixed up name for cpu@3 -> cpu
(XEN) fixed up name for power-domains -> power-domains
(XEN) fixed up name for pd-usb0 -> pd-usb0
(XEN) fixed up name for pd-usb1 -> pd-usb1
(XEN) fixed up name for pd-sata -> pd-sata
(XEN) fixed up name for pd-spi0 -> pd-spi0
(XEN) fixed up name for pd-spi1 -> pd-spi1
(XEN) fixed up name for pd-uart0 -> pd-uart0
(XEN) fixed up name for pd-uart1 -> pd-uart1
(XEN) fixed up name for pd-eth0 -> pd-eth0
(XEN) fixed up name for pd-eth1 -> pd-eth1
(XEN) fixed up name for pd-eth2 -> pd-eth2
(XEN) fixed up name for pd-eth3 -> pd-eth3
(XEN) fixed up name for pd-i2c0 -> pd-i2c0
(XEN) fixed up name for pd-i2c1 -> pd-i2c1
(XEN) fixed up name for pd-dp -> pd-dp
(XEN) fixed up name for pd-gdma -> pd-gdma
(XEN) fixed up name for pd-adma -> pd-adma
(XEN) fixed up name for pd-ttc0 -> pd-ttc0
(XEN) fixed up name for pd-ttc1 -> pd-ttc1
(XEN) fixed up name for pd-ttc2 -> pd-ttc2
(XEN) fixed up name for pd-ttc3 -> pd-ttc3
(XEN) fixed up name for pd-sd0 -> pd-sd0
(XEN) fixed up name for pd-sd1 -> pd-sd1
(XEN) fixed up name for pd-nand -> pd-nand
(XEN) fixed up name for pd-qspi -> pd-qspi
(XEN) fixed up name for pd-gpio -> pd-gpio
(XEN) fixed up name for pd-can0 -> pd-can0
(XEN) fixed up name for pd-can1 -> pd-can1
(XEN) fixed up name for pd-ddr -> pd-ddr
(XEN) fixed up name for pd-apll -> pd-apll
(XEN) fixed up name for pd-vpll -> pd-vpll
(XEN) fixed up name for pd-dpll -> pd-dpll
(XEN) fixed up name for pd-rpll -> pd-rpll
(XEN) fixed up name for pd-iopll -> pd-iopll
(XEN) fixed up name for pmu -> pmu
(XEN) fixed up name for psci -> psci
(XEN) fixed up name for firmware -> firmware
(XEN) fixed up name for timer -> timer
(XEN) fixed up name for amba_apu -> amba_apu
(XEN) fixed up name for interrupt-controller@f9010000 -> interrupt-controller
(XEN) fixed up name for amba -> amba
(XEN) fixed up name for can@ff060000 -> can
(XEN) fixed up name for can@ff070000 -> can
(XEN) fixed up name for cci@fd6e0000 -> cci
(XEN) fixed up name for pmu@9000 -> pmu
(XEN) fixed up name for dma@fd500000 -> dma
(XEN) fixed up name for dma@fd510000 -> dma
(XEN) fixed up name for dma@fd520000 -> dma
(XEN) fixed up name for dma@fd530000 -> dma
(XEN) fixed up name for dma@fd540000 -> dma
(XEN) fixed up name for dma@fd550000 -> dma
(XEN) fixed up name for dma@fd560000 -> dma
(XEN) fixed up name for dma@fd570000 -> dma
(XEN) fixed up name for gpu@fd4b0000 -> gpu
(XEN) fixed up name for dma@ffa80000 -> dma
(XEN) fixed up name for dma@ffa90000 -> dma
(XEN) fixed up name for dma@ffaa0000 -> dma
(XEN) fixed up name for dma@ffab0000 -> dma
(XEN) fixed up name for dma@ffac0000 -> dma
(XEN) fixed up name for dma@ffad0000 -> dma
(XEN) fixed up name for dma@ffae0000 -> dma
(XEN) fixed up name for dma@ffaf0000 -> dma
(XEN) fixed up name for memory-controller@fd070000 -> memory-controller
(XEN) fixed up name for nand@ff100000 -> nand
(XEN) fixed up name for ethernet@ff0b0000 -> ethernet
(XEN) fixed up name for ethernet@ff0c0000 -> ethernet
(XEN) fixed up name for ethernet@ff0d0000 -> ethernet
(XEN) fixed up name for ethernet@ff0e0000 -> ethernet
(XEN) fixed up name for phy@c -> phy
(XEN) fixed up name for gpio@ff0a0000 -> gpio
(XEN) fixed up name for i2c@ff020000 -> i2c
(XEN) fixed up name for gpio@20 -> gpio
(XEN) fixed up name for gpio@21 -> gpio
(XEN) fixed up name for i2cswitch@75 -> i2cswitch
(XEN) fixed up name for i2c@0 -> i2c
(XEN) fixed up name for ina226@40 -> ina226
(XEN) fixed up name for ina226@41 -> ina226
(XEN) fixed up name for ina226@42 -> ina226
(XEN) fixed up name for ina226@43 -> ina226
(XEN) fixed up name for ina226@44 -> ina226
(XEN) fixed up name for ina226@45 -> ina226
(XEN) fixed up name for ina226@46 -> ina226
(XEN) fixed up name for ina226@47 -> ina226
(XEN) fixed up name for ina226@4a -> ina226
(XEN) fixed up name for ina226@4b -> ina226
(XEN) fixed up name for i2c@1 -> i2c
(XEN) fixed up name for ina226@40 -> ina226
(XEN) fixed up name for ina226@41 -> ina226
(XEN) fixed up name for ina226@42 -> ina226
(XEN) fixed up name for ina226@43 -> ina226
(XEN) fixed up name for ina226@44 -> ina226
(XEN) fixed up name for ina226@45 -> ina226
(XEN) fixed up name for ina226@46 -> ina226
(XEN) fixed up name for ina226@47 -> ina226
(XEN) fixed up name for i2c@2 -> i2c
(XEN) fixed up name for max15301@a -> max15301
(XEN) fixed up name for max15303@b -> max15303
(XEN) fixed up name for max15303@10 -> max15303
(XEN) fixed up name for max15301@13 -> max15301
(XEN) fixed up name for max15303@14 -> max15303
(XEN) fixed up name for max15303@15 -> max15303
(XEN) fixed up name for max15303@16 -> max15303
(XEN) fixed up name for max15303@17 -> max15303
(XEN) fixed up name for max15301@18 -> max15301
(XEN) fixed up name for max15303@1a -> max15303
(XEN) fixed up name for max15303@1d -> max15303
(XEN) fixed up name for max15303@20 -> max15303
(XEN) fixed up name for max20751@72 -> max20751
(XEN) fixed up name for max20751@73 -> max20751
(XEN) fixed up name for i2c@ff030000 -> i2c
(XEN) fixed up name for i2cswitch@74 -> i2cswitch
(XEN) fixed up name for i2c@0 -> i2c
(XEN) fixed up name for eeprom@54 -> eeprom
(XEN) fixed up name for eeprom@55 -> eeprom
(XEN) fixed up name for eeprom@56 -> eeprom
(XEN) fixed up name for eeprom@57 -> eeprom
(XEN) fixed up name for i2c@1 -> i2c
(XEN) fixed up name for clock-generator1@36 -> clock-generator1
(XEN) fixed up name for i2c@2 -> i2c
(XEN) fixed up name for clock-generator2@5d -> clock-generator2
(XEN) fixed up name for i2c@3 -> i2c
(XEN) fixed up name for clock-generator3@5d -> clock-generator3
(XEN) fixed up name for i2c@4 -> i2c
(XEN) fixed up name for clock-generator4@69 -> clock-generator4
(XEN) fixed up name for i2cswitch@75 -> i2cswitch
(XEN) fixed up name for i2c@0 -> i2c
(XEN) fixed up name for i2c@1 -> i2c
(XEN) fixed up name for i2c@2 -> i2c
(XEN) fixed up name for i2c@3 -> i2c
(XEN) fixed up name for dev@19 -> dev
(XEN) fixed up name for dev@30 -> dev
(XEN) fixed up name for dev@35 -> dev
(XEN) fixed up name for dev@36 -> dev
(XEN) fixed up name for dev@51 -> dev
(XEN) fixed up name for i2c@4 -> i2c
(XEN) fixed up name for i2c@5 -> i2c
(XEN) fixed up name for i2c@6 -> i2c
(XEN) fixed up name for i2c@7 -> i2c
(XEN) fixed up name for pcie@fd0e0000 -> pcie
(XEN) fixed up name for legacy-interrupt-controller -> legacy-interrupt-controller
(XEN) fixed up name for spi@ff0f0000 -> spi
(XEN) fixed up name for flash@0 -> flash
(XEN) fixed up name for partition@0x00000000 -> partition
(XEN) fixed up name for partition@0x01e00000 -> partition
(XEN) fixed up name for partition@0x01e40000 -> partition
(XEN) fixed up name for partition@0x03840000 -> partition
(XEN) fixed up name for partition@qspi-fsbl-uboot -> partition
(XEN) fixed up name for partition@qspi-linux -> partition
(XEN) fixed up name for partition@qspi-device-tree -> partition
(XEN) fixed up name for partition@qspi-rootfs -> partition
(XEN) fixed up name for rtc@ffa60000 -> rtc
(XEN) fixed up name for ahci@fd0c0000 -> ahci
(XEN) fixed up name for sdhci@ff160000 -> sdhci
(XEN) fixed up name for sdhci@ff170000 -> sdhci
(XEN) fixed up name for smmu@fd800000 -> smmu
(XEN) fixed up name for spi@ff040000 -> spi
(XEN) fixed up name for spi@ff050000 -> spi
(XEN) fixed up name for timer@ff110000 -> timer
(XEN) fixed up name for timer@ff120000 -> timer
(XEN) fixed up name for timer@ff130000 -> timer
(XEN) fixed up name for timer@ff140000 -> timer
(XEN) fixed up name for serial@ff000000 -> serial
(XEN) fixed up name for serial@ff010000 -> serial
(XEN) fixed up name for usb@fe200000 -> usb
(XEN) fixed up name for dwc3@fe200000 -> dwc3
(XEN) fixed up name for usb@fe300000 -> usb
(XEN) fixed up name for dwc3@fe300000 -> dwc3
(XEN) fixed up name for watchdog@fd4d0000 -> watchdog
(XEN) fixed up name for xilinx_drm -> xilinx_drm
(XEN) fixed up name for planes -> planes
(XEN) fixed up name for plane0 -> plane0
(XEN) fixed up name for plane1 -> plane1
(XEN) fixed up name for dp@fd4a0000 -> dp
(XEN) fixed up name for dp_snd_card -> dp_snd_card
(XEN) fixed up name for dp_snd_codec0 -> dp_snd_codec0
(XEN) fixed up name for dp_snd_pcm0 -> dp_snd_pcm0
(XEN) fixed up name for dp_snd_pcm1 -> dp_snd_pcm1
(XEN) fixed up name for dp_sub@fd4aa000 -> dp_sub
(XEN) fixed up name for dma@fd4c0000 -> dma
(XEN) fixed up name for dma-video0channel@fd4c0000 -> dma-video0channel
(XEN) fixed up name for dma-video1channel@fd4c0000 -> dma-video1channel
(XEN) fixed up name for dma-video2channel@fd4c0000 -> dma-video2channel
(XEN) fixed up name for dma-graphicschannel@fd4c0000 -> dma-graphicschannel
(XEN) fixed up name for dma-audio0channel@fd4c0000 -> dma-audio0channel
(XEN) fixed up name for dma-audio1channel@fd4c0000 -> dma-audio1channel
(XEN) fixed up name for clk100 -> clk100
(XEN) fixed up name for clk125 -> clk125
(XEN) fixed up name for clk200 -> clk200
(XEN) fixed up name for clk250 -> clk250
(XEN) fixed up name for clk300 -> clk300
(XEN) fixed up name for clk600 -> clk600
(XEN) fixed up name for clock0 -> clock0
(XEN) fixed up name for clock1 -> clock1
(XEN) fixed up name for dpdma_clk -> dpdma_clk
(XEN) fixed up name for drm_clock -> drm_clock
(XEN) fixed up name for ocm -> ocm
(XEN) fixed up name for aliases -> aliases
(XEN) fixed up name for chosen -> chosen
(XEN) fixed up name for dom0 -> dom0
(XEN) fixed up name for memory -> memory
(XEN)  <- unflatten_device_tree()
(XEN) adding DT alias:serial0: stem=serial id=0 node=/amba/serial@ff000000
(XEN) adding DT alias:ethernet0: stem=ethernet id=0 node=/amba/ethernet@ff0e0000
(XEN) adding DT alias:spi0: stem=spi id=0 node=/amba/spi@ff0f0000
(XEN) adding DT alias:rtc0: stem=rtc id=0 node=/amba/rtc@ffa60000
(XEN) Platform: Xilinx ZynqMP
(XEN) Looking for dtuart at "serial0", options ""
(XEN) DT: ** translation for device /amba/serial@ff000000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff000000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff000000
(XEN) DT: one level translation:<3> 00000000<3> ff000000<3>
(XEN) DT: reached root node
(XEN) dt_device_get_raw_irq: dev=/amba/serial@ff000000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000015...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controlXen 4.7.0-rc
(XEN) Xen version 4.7.0-rc (edgar@) (aarch64-none-elf-gcc (Linaro GCC 2014.05) 4.9.1 20140422 (prerelease)) debug=y Sat May 14 20:42:36 CEST 2016
(XEN) Latest ChangeSet: Tue May 10 19:14:34 2016 +0100 git:c79fc6c-dirty
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000002222 0000000000000000
(XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010305106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000001122 0000000000000000
(XEN)   ISA Features:  0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01260000 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using PSCI-1.0 for SMP bringup
(XEN) dt_device_get_raw_irq: dev=/timer, index=0
(XEN)  intspec=1 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000001 0x0000000d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/timer, index=1
(XEN)  intspec=1 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000001 0x0000000e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/timer, index=2
(XEN)  intspec=1 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000001 0x0000000b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/timer, index=3
(XEN)  intspec=1 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000001 0x0000000a...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 100000 KHz
(XEN) DT: ** translation for device /amba_apu/interrupt-controller@f9010000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba_apu
(XEN) DT: translating address:<3> 00000000<3> f9010000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: f9010000
(XEN) DT: one level translation:<3> 00000000<3> f9010000<3>
(XEN) DT: reached root node
(XEN) DT: ** translation for device /amba_apu/interrupt-controller@f9010000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba_apu
(XEN) DT: translating address:<3> 00000000<3> f902f000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: f902f000
(XEN) DT: one level translation:<3> 00000000<3> f902f000<3>
(XEN) DT: reached root node
(XEN) DT: ** translation for device /amba_apu/interrupt-controller@f9010000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba_apu
(XEN) DT: translating address:<3> 00000000<3> f9040000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: f9040000
(XEN) DT: one level translation:<3> 00000000<3> f9040000<3>
(XEN) DT: reached root node
(XEN) DT: ** translation for device /amba_apu/interrupt-controller@f9010000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba_apu
(XEN) DT: translating address:<3> 00000000<3> f906f000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: f906f000
(XEN) DT: one level translation:<3> 00000000<3> f906f000<3>
(XEN) DT: reached root node
(XEN) dt_device_get_raw_irq: dev=/amba_apu/interrupt-controller@f9010000, index=0
(XEN)  intspec=1 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000001 0x00000009...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000f9010000
(XEN)         gic_cpu_addr=00000000f902f000
(XEN)         gic_hyp_addr=00000000f9040000
(XEN)         gic_vcpu_addr=00000000f906f000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 192 lines, 4 cpus, secure (IID 0200143b).
(XEN) GICv2: WARNING: CPU0: Failed to configure IRQ26 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU0: Failed to configure IRQ27 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU0: Failed to configure IRQ30 as Edge-triggered. H/w forces to Level-triggered.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 32 KiB.
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) GICv2: WARNING: CPU1: Failed to configure IRQ26 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU1: Failed to configure IRQ27 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU1: Failed to configure IRQ30 as Edge-triggered. H/w forces to Level-triggered.
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 00000002 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) GICv2: WARNING: CPU2: Failed to configure IRQ26 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU2: Failed to configure IRQ27 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU2: Failed to configure IRQ30 as Edge-triggered. H/w forces to Level-triggered.
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 00000003 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) GICv2: WARNING: CPU3: Failed to configure IRQ26 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU3: Failed to configure IRQ27 as Edge-triggered. H/w forces to Level-triggered.
(XEN) GICv2: WARNING: CPU3: Failed to configure IRQ30 as Edge-triggered. H/w forces to Level-triggered.
(XEN) CPU 3 booted.
(XEN) Brought up 4 CPUs
(XEN) P2M: 40-bit IPA with 40-bit PA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) DT: ** translation for device /amba/smmu@fd800000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd800000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd800000
(XEN) DT: one level translation:<3> 00000000<3> fd800000<3>
(XEN) DT: reached root node
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=0
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=1
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=2
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=3
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=4
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=5
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=6
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=7
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=8
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=9
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=10
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=11
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=12
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=13
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=14
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=15
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=16
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=17
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=0
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=1
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=2
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=3
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=4
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=5
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=6
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=7
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=8
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=9
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=10
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=11
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=12
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=13
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=14
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=15
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/smmu@fd800000, index=16
(XEN)  intspec=0 intlen=51
(XEN)  intsize=3 intlen=51
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000009b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) smmu: /amba/smmu@fd800000: probing hardware configuration...
(XEN) smmu: /amba/smmu@fd800000: SMMUv2 with:
(XEN) smmu: /amba/smmu@fd800000: 	stage 2 translation
(XEN) smmu: /amba/smmu@fd800000: 	stream matching with 48 register groups, mask 0x7fff
(XEN) smmu: /amba/smmu@fd800000: 	16 context banks (0 stage-2 only)
(XEN) smmu: /amba/smmu@fd800000: 	Stage-2: 40-bit IPA -> 48-bit PA
(XEN) smmu: /amba/smmu@fd800000: registered 4 master devices
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 0000000000080000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000040000000 (512MB)
(XEN) Grant table range: 0x0000007fe00000-0x0000007fe5f000
(XEN) dt_irq_number: dev=/
(XEN) dt_irq_number: dev=/power-domains
(XEN) dt_irq_number: dev=/power-domains/pd-usb0
(XEN) dt_irq_number: dev=/power-domains/pd-usb1
(XEN) dt_irq_number: dev=/power-domains/pd-sata
(XEN) dt_irq_number: dev=/power-domains/pd-spi0
(XEN) dt_irq_number: dev=/power-domains/pd-spi1
(XEN) dt_irq_number: dev=/power-domains/pd-uart0
(XEN) dt_irq_number: dev=/power-domains/pd-uart1
(XEN) dt_irq_number: dev=/power-domains/pd-eth0
(XEN) dt_irq_number: dev=/power-domains/pd-eth1
(XEN) dt_irq_number: dev=/power-domains/pd-eth2
(XEN) dt_irq_number: dev=/power-domains/pd-eth3
(XEN) dt_irq_number: dev=/power-domains/pd-i2c0
(XEN) dt_irq_number: dev=/power-domains/pd-i2c1
(XEN) dt_irq_number: dev=/power-domains/pd-dp
(XEN) dt_irq_number: dev=/power-domains/pd-gdma
(XEN) dt_irq_number: dev=/power-domains/pd-adma
(XEN) dt_irq_number: dev=/power-domains/pd-ttc0
(XEN) dt_irq_number: dev=/power-domains/pd-ttc1
(XEN) dt_irq_number: dev=/power-domains/pd-ttc2
(XEN) dt_irq_number: dev=/power-domains/pd-ttc3
(XEN) dt_irq_number: dev=/power-domains/pd-sd0
(XEN) dt_irq_number: dev=/power-domains/pd-sd1
(XEN) dt_irq_number: dev=/power-domains/pd-nand
(XEN) dt_irq_number: dev=/power-domains/pd-qspi
(XEN) dt_irq_number: dev=/power-domains/pd-gpio
(XEN) dt_irq_number: dev=/power-domains/pd-can0
(XEN) dt_irq_number: dev=/power-domains/pd-can1
(XEN) dt_irq_number: dev=/power-domains/pd-ddr
(XEN) dt_irq_number: dev=/power-domains/pd-apll
(XEN) dt_irq_number: dev=/power-domains/pd-vpll
(XEN) dt_irq_number: dev=/power-domains/pd-dpll
(XEN) dt_irq_number: dev=/power-domains/pd-rpll
(XEN) dt_irq_number: dev=/power-domains/pd-iopll
(XEN) dt_irq_number: dev=/amba_apu
(XEN) dt_irq_number: dev=/amba
(XEN) dt_irq_number: dev=/amba/can@ff060000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/can@ff060000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000017...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/can@ff060000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000017...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/can@ff060000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff060000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff060000
(XEN) DT: one level translation:<3> 00000000<3> ff060000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/can@ff070000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/can@ff070000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000018...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/can@ff070000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000018...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/can@ff070000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff070000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff070000
(XEN) DT: one level translation:<3> 00000000<3> ff070000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/cci@fd6e0000
(XEN) DT: ** translation for device /amba/cci@fd6e0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd6e0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd6e0000
(XEN) DT: one level translation:<3> 00000000<3> fd6e0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/cci@fd6e0000/pmu@9000
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=0
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=0
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=1
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=1
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=2
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=2
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=3
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=3
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=4
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/cci@fd6e0000/pmu@9000, index=4
(XEN)  intspec=0 intlen=15
(XEN)  intsize=3 intlen=15
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/cci@fd6e0000/pmu@9000 **
(XEN) DT: bus is default (na=1, ns=1) on /amba/cci@fd6e0000
(XEN) DT: translating address:<3> 00009000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /amba
(XEN) DT: walking ranges...
(XEN) DT: default map, cp=0, s=10000, da=9000
(XEN) DT: parent translation for:<3> 00000000<3> fd6e0000<3>
(XEN) DT: with offset: 9000
(XEN) DT: one level translation:<3> 00000000<3> fd6e9000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd6e9000
(XEN) DT: one level translation:<3> 00000000<3> fd6e9000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd500000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd500000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007c...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd500000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007c...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd500000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd500000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd500000
(XEN) DT: one level translation:<3> 00000000<3> fd500000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd510000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd510000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd510000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd510000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd510000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd510000
(XEN) DT: one level translation:<3> 00000000<3> fd510000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd520000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd520000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd520000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd520000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd520000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd520000
(XEN) DT: one level translation:<3> 00000000<3> fd520000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd530000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd530000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd530000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000007f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd530000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd530000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd530000
(XEN) DT: one level translation:<3> 00000000<3> fd530000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd540000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd540000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000080...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd540000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000080...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd540000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd540000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd540000
(XEN) DT: one level translation:<3> 00000000<3> fd540000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd550000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd550000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000081...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd550000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000081...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd550000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd550000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd550000
(XEN) DT: one level translation:<3> 00000000<3> fd550000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd560000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd560000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000082...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd560000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000082...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd560000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd560000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd560000
(XEN) DT: one level translation:<3> 00000000<3> fd560000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@fd570000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd570000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000083...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@fd570000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000083...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@fd570000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd570000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd570000
(XEN) DT: one level translation:<3> 00000000<3> fd570000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/gpu@fd4b0000
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=0
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=0
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=1
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=1
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=2
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=2
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=3
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=3
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=4
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=4
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=5
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpu@fd4b0000, index=5
(XEN)  intspec=0 intlen=18
(XEN)  intsize=3 intlen=18
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000084...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/gpu@fd4b0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd4b0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd4b0000
(XEN) DT: one level translation:<3> 00000000<3> fd4b0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffa80000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffa80000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000004d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffa80000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000004d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffa80000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffa80000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffa80000
(XEN) DT: one level translation:<3> 00000000<3> ffa80000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffa90000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffa90000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000004e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffa90000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000004e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffa90000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffa90000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffa90000
(XEN) DT: one level translation:<3> 00000000<3> ffa90000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffaa0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffaa0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000004f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffaa0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000004f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffaa0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffaa0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffaa0000
(XEN) DT: one level translation:<3> 00000000<3> ffaa0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffab0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffab0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000050...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffab0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000050...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffab0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffab0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffab0000
(XEN) DT: one level translation:<3> 00000000<3> ffab0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffac0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffac0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000051...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffac0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000051...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffac0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffac0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffac0000
(XEN) DT: one level translation:<3> 00000000<3> ffac0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffad0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffad0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000052...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffad0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000052...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffad0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffad0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffad0000
(XEN) DT: one level translation:<3> 00000000<3> ffad0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffae0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffae0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000053...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffae0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000053...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffae0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffae0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffae0000
(XEN) DT: one level translation:<3> 00000000<3> ffae0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/dma@ffaf0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffaf0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000054...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/dma@ffaf0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000054...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/dma@ffaf0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ffaf0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ffaf0000
(XEN) DT: one level translation:<3> 00000000<3> ffaf0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/memory-controller@fd070000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/memory-controller@fd070000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000070...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/memory-controller@fd070000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000070...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/memory-controller@fd070000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd070000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd070000
(XEN) DT: one level translation:<3> 00000000<3> fd070000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/nand@ff100000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/nand@ff100000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000000e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/nand@ff100000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000000e...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/nand@ff100000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff100000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff100000
(XEN) DT: one level translation:<3> 00000000<3> ff100000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/ethernet@ff0b0000
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) smmu: /amba/smmu@fd800000: d0: p2maddr 0x000000007ff64000
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0b0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000039...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0b0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000039...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0b0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000039...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0b0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000039...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/ethernet@ff0b0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff0b0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff0b0000
(XEN) DT: one level translation:<3> 00000000<3> ff0b0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/ethernet@ff0c0000
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0c0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0c0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0c0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0c0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003b...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/ethernet@ff0c0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff0c0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff0c0000
(XEN) DT: one level translation:<3> 00000000<3> ff0c0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/ethernet@ff0d0000
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0d0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0d0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0d0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0d0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003d...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/ethernet@ff0d0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff0d0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff0d0000
(XEN) DT: one level translation:<3> 00000000<3> ff0d0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/ethernet@ff0e0000
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0e0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0e0000, index=0
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0e0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/ethernet@ff0e0000, index=1
(XEN)  intspec=0 intlen=6
(XEN)  intsize=3 intlen=6
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x0000003f...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/ethernet@ff0e0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff0e0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff0e0000
(XEN) DT: one level translation:<3> 00000000<3> ff0e0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/ethernet@ff0e0000/phy@c
(XEN) dt_irq_number: dev=/amba/gpio@ff0a0000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/gpio@ff0a0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000010...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/gpio@ff0a0000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000010...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/gpio@ff0a0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff0a0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff0a0000
(XEN) DT: one level translation:<3> 00000000<3> ff0a0000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/i2c@ff020000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/i2c@ff020000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000011...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/i2c@ff020000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000011...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/i2c@ff020000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff020000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff020000
(XEN) DT: one level translation:<3> 00000000<3> ff020000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/gpio@20
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/gpio@21
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@40
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@41
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@42
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@43
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@44
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@45
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@46
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@47
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@4a
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@0/ina226@4b
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@40
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@41
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@42
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@43
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@44
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@45
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@46
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@1/ina226@47
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15301@a
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@b
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@10
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15301@13
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@14
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@15
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@16
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@17
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15301@18
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@1a
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@1d
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max15303@20
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max20751@72
(XEN) dt_irq_number: dev=/amba/i2c@ff020000/i2cswitch@75/i2c@2/max20751@73
(XEN) dt_irq_number: dev=/amba/i2c@ff030000
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_device_get_raw_irq: dev=/amba/i2c@ff030000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000012...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/i2c@ff030000, index=0
(XEN)  intspec=0 intlen=3
(XEN)  intsize=3 intlen=3
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000012...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/i2c@ff030000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> ff030000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: ff030000
(XEN) DT: one level translation:<3> 00000000<3> ff030000<3>
(XEN) DT: reached root node
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@0
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@0/eeprom@54
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@0/eeprom@55
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@0/eeprom@56
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@0/eeprom@57
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@1
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@1/clock-generator1@36
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@2
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@2/clock-generator2@5d
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@3
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@3/clock-generator3@5d
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@4
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@74/i2c@4/clock-generator4@69
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@0
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@1
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@2
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@3
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@3/dev@19
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@3/dev@30
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@3/dev@35
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@3/dev@36
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@3/dev@51
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@4
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@5
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@6
(XEN) dt_irq_number: dev=/amba/i2c@ff030000/i2cswitch@75/i2c@7
(XEN) dt_irq_number: dev=/amba/pcie@fd0e0000
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=0
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000076...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=0
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000076...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=1
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000074...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=1
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000074...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=2
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000073...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=2
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000073...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=3
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000072...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) dt_device_get_raw_irq: dev=/amba/pcie@fd0e0000, index=3
(XEN)  intspec=0 intlen=12
(XEN)  intsize=3 intlen=12
(XEN) dt_irq_map_raw: par=/amba_apu/interrupt-controller@f9010000,intspec=[0x00000000 0x00000072...],ointsize=3
(XEN) dt_irq_map_raw: ipar=/amba_apu/interrupt-controller@f9010000, size=3
(XEN)  -> addrsize=2
(XEN)  -> got it !
(XEN) DT: ** translation for device /amba/pcie@fd0e0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd0e0000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd0e0000
(XEN) DT: one level translation:<3> 00000000<3> fd0e0000<3>
(XEN) DT: reached root node
(XEN) DT: ** translation for device /amba/pcie@fd0e0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> fd480000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: fd480000
(XEN) DT: one level translation:<3> 00000000<3> fd480000<3>
(XEN) DT: reached root node
(XEN) DT: ** translation for device /amba/pcie@fd0e0000 **
(XEN) DT: bus is default (na=2, ns=2) on /amba
(XEN) DT: translating address:<3> 00000000<3> e0000000<3>
(XEN) DT: parent bus is default (na=2, ns=2) on /
(XEN) DT: empty ranges; 1:1 translation
(XEN) DT: parent translation for:<3> 00000000<3> 00000000<3>
(XEN) DT: with offset: e0000000
(XEN) DT: one level translation:<3> 00000000<3> e0000000<3>
(XEN) DT: reached root node
(XEN) dt_for_each_irq_map: par=/amba/pcie@fd0e0000 cb=0000000000247118 data=000080007ffd4000
(XEN) dt_for_each_irq_map: ipar=/amba/pcie@fd0e0000, size=1
(XEN)  -> addrsize=3
(XEN)  -> ipar legacy-interrupt-controller
(XEN)  -> pintsize=1, paddrsize=0
(XEN)  -> failed to translate IRQ: -22
(XEN) Device tree generation failed (-22).
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Could not set up DOM0 guest OS
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply related	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2016-05-14 19:04   ` Edgar E. Iglesias
@ 2016-05-16  9:58     ` Wei Liu
  2016-05-16 13:20     ` Julien Grall
  1 sibling, 0 replies; 28+ messages in thread
From: Wei Liu @ 2016-05-16  9:58 UTC (permalink / raw)
  To: Edgar E. Iglesias; +Cc: Julien Grall, Stefano Stabellini, Wei Liu, Xen-devel

On Sat, May 14, 2016 at 09:04:35PM +0200, Edgar E. Iglesias wrote:
[...]
> > Was PCIe working on Xen 4.6? If yes, it's the regression and we could
> > consider it as a blocker for the release (CC Wei for that).
> 
> No, these PCIe nodes were added recently.
> The device tree bindings were different before but after discussing
> with the upstream Linux folks they got changed.
> 

OK, so this is not a blocker for 4.7.

It would be OK to have a board specific quirk for 4.7 though so that
people just don't blindly stumble upon this issue. From my point of view
I would happily accept one such patch because you're the de facto
maintainer of that board. :-)

Anything that touches common code will be scrutinised though. The patch
you posted looks very hacky to me at first glance.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2016-05-14 19:04   ` Edgar E. Iglesias
  2016-05-16  9:58     ` Wei Liu
@ 2016-05-16 13:20     ` Julien Grall
  2016-05-16 13:41       ` Edgar E. Iglesias
  1 sibling, 1 reply; 28+ messages in thread
From: Julien Grall @ 2016-05-16 13:20 UTC (permalink / raw)
  To: Edgar E. Iglesias; +Cc: Stefano Stabellini, Wei Liu, Xen-devel

Hello Edgar,

On 14/05/16 20:04, Edgar E. Iglesias wrote:
> On Sat, May 14, 2016 at 07:15:55PM +0100, Julien Grall wrote:
> You can see that it is used in the interrupt-map properties.
> IIUC, the interrupt lines connected to the pcie_intc controller
> are simply going to be combined into the "intx" line IRQ 116 on
> going from the pcie bridge towards the gic.
>
> I don't think we need to do much than to ignore the node but what
> we present to dom0 must look the same..

I think you are right. I expect the platform to only have one main 
interrupt controller (i.e the GIC), the others would be connected to the 
main one.

Therefore, the interrupts will have no meaning for the GIC and could be 
ignored.

FWIW, we already have a such check in handle_device.

>
>>
>>>
>>> Disabling the pcie node for zynqmp boards gets dom0 to boot (obviously
>>> without PCIe support).
>>>
>>> Does it make sense to try to fix this problem this late inte the
>>> release cycle? (I can have a closer look and propose a possible fix
>>> for discussion)
>>
>> I would try to fix it in Xen 4.7 if the patch is simple. Otherwise we could
>> backport it after the release.
>
> OK, great.
> I'll have a closer look too then.
>
> I was trying this, but it may be too permissive:
>
> diff --git a/xen/common/device_tree.c b/xen/common/device_tree.c
> index 0ed86a7..68cb162 100644
> --- a/xen/common/device_tree.c
> +++ b/xen/common/device_tree.c
> @@ -1176,6 +1176,15 @@ int dt_for_each_irq_map(const struct dt_device_node *dev,
>           for ( i = 0; i < pintsize; i++ )
>               dt_raw_irq.specifier[i] = dt_read_number(imap + i, 1);
>
> +        if (dt_raw_irq.controller != dt_interrupt_controller) {

Coding style.

> +            /* If this is not the main interrupt controller, we assume
> +             * it's part of a bus-bridge and ignore remapping IRQs for it.
> +             * Xen only supports one interrupt controller at the moment.  */

This comment is not true for every case. The interrupt controller may 
not be part of the bus-bridge.

One platform with multiple interrupt controller, I expect to always see 
one main controller, the others would be connected to the main one. So, 
the interrupt will have no meaning for the GIC.

> +            imap += pintsize;
> +            imaplen -= pintsize;

I would add a dt_printk to mention that the IRQ has been skipped.

> +            continue;
> +        }

Please send a formal patch to the ML. What would be the drawback if this 
patch doesn't reach Xen 4.7? I.e Are PCI devices necessary to run the 
platform?

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2016-05-16 13:20     ` Julien Grall
@ 2016-05-16 13:41       ` Edgar E. Iglesias
  2016-05-16 13:43         ` Julien Grall
  0 siblings, 1 reply; 28+ messages in thread
From: Edgar E. Iglesias @ 2016-05-16 13:41 UTC (permalink / raw)
  To: Julien Grall; +Cc: Stefano Stabellini, Wei Liu, Xen-devel

On Mon, May 16, 2016 at 02:20:24PM +0100, Julien Grall wrote:
> Hello Edgar,
> 
> On 14/05/16 20:04, Edgar E. Iglesias wrote:
> >On Sat, May 14, 2016 at 07:15:55PM +0100, Julien Grall wrote:
> >You can see that it is used in the interrupt-map properties.
> >IIUC, the interrupt lines connected to the pcie_intc controller
> >are simply going to be combined into the "intx" line IRQ 116 on
> >going from the pcie bridge towards the gic.
> >
> >I don't think we need to do much than to ignore the node but what
> >we present to dom0 must look the same..
> 
> I think you are right. I expect the platform to only have one main interrupt
> controller (i.e the GIC), the others would be connected to the main one.
> 
> Therefore, the interrupts will have no meaning for the GIC and could be
> ignored.
> 
> FWIW, we already have a such check in handle_device.

Thanks Julien, I'll have a look at handle_device.


> 
> >
> >>
> >>>
> >>>Disabling the pcie node for zynqmp boards gets dom0 to boot (obviously
> >>>without PCIe support).
> >>>
> >>>Does it make sense to try to fix this problem this late inte the
> >>>release cycle? (I can have a closer look and propose a possible fix
> >>>for discussion)
> >>
> >>I would try to fix it in Xen 4.7 if the patch is simple. Otherwise we could
> >>backport it after the release.
> >
> >OK, great.
> >I'll have a closer look too then.
> >
> >I was trying this, but it may be too permissive:
> >
> >diff --git a/xen/common/device_tree.c b/xen/common/device_tree.c
> >index 0ed86a7..68cb162 100644
> >--- a/xen/common/device_tree.c
> >+++ b/xen/common/device_tree.c
> >@@ -1176,6 +1176,15 @@ int dt_for_each_irq_map(const struct dt_device_node *dev,
> >          for ( i = 0; i < pintsize; i++ )
> >              dt_raw_irq.specifier[i] = dt_read_number(imap + i, 1);
> >
> >+        if (dt_raw_irq.controller != dt_interrupt_controller) {
> 
> Coding style.
> 
> >+            /* If this is not the main interrupt controller, we assume
> >+             * it's part of a bus-bridge and ignore remapping IRQs for it.
> >+             * Xen only supports one interrupt controller at the moment.  */
> 
> This comment is not true for every case. The interrupt controller may not be
> part of the bus-bridge.
> 
> One platform with multiple interrupt controller, I expect to always see one
> main controller, the others would be connected to the main one. So, the
> interrupt will have no meaning for the GIC.
> 
> >+            imap += pintsize;
> >+            imaplen -= pintsize;
> 
> I would add a dt_printk to mention that the IRQ has been skipped.
> 
> >+            continue;
> >+        }
> 
> Please send a formal patch to the ML. What would be the drawback if this
> patch doesn't reach Xen 4.7? I.e Are PCI devices necessary to run the
> platform?

No, they are not necessary. We have a few options.

1. If we do nothing, the ZynqMP boards with PCIe support won't even boot
   dom0.

2. A safe option is to disable the PCIe node in the ZynqMP platform.
   That'll boot dom0 but PCIe won't be functional.

3. If we get something like this patch in, we'll get dom0 to boot with
   PCIe support hopefully working in dom0.

Thanks for the review. I'll spin a proper patch and we can discuss/consider
if it's worth merging for 4.7 or if we go with option nr 2.

Best regards,
Edgar

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2016-05-16 13:41       ` Edgar E. Iglesias
@ 2016-05-16 13:43         ` Julien Grall
  0 siblings, 0 replies; 28+ messages in thread
From: Julien Grall @ 2016-05-16 13:43 UTC (permalink / raw)
  To: Edgar E. Iglesias; +Cc: Stefano Stabellini, Wei Liu, Xen-devel



On 16/05/16 14:41, Edgar E. Iglesias wrote:
> On Mon, May 16, 2016 at 02:20:24PM +0100, Julien Grall wrote:
> No, they are not necessary. We have a few options.
>
> 1. If we do nothing, the ZynqMP boards with PCIe support won't even boot
>     dom0.
>
> 2. A safe option is to disable the PCIe node in the ZynqMP platform.
>     That'll boot dom0 but PCIe won't be functional.
>
> 3. If we get something like this patch in, we'll get dom0 to boot with
>     PCIe support hopefully working in dom0.
>
> Thanks for the review. I'll spin a proper patch and we can discuss/consider
> if it's worth merging for 4.7 or if we go with option nr 2.

Please mention the options in the patch, and if possible the pros/cons.

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2017-05-25 10:17 ` Julien Grall
@ 2017-05-25 18:41   ` Stefano Stabellini
  0 siblings, 0 replies; 28+ messages in thread
From: Stefano Stabellini @ 2017-05-25 18:41 UTC (permalink / raw)
  To: Julien Grall; +Cc: Stefano Stabellini, Andrii Anisov, Xen Devel

On Thu, 25 May 2017, Julien Grall wrote:
> Hi Andrii,
> 
> On 23/05/17 18:03, Andrii Anisov wrote:
> > * Hardware:
> > Salvator-X board with Renesas R-Car H3 SoC (ARM64)
> > 
> > * Software:
> > XEN 4.9-rc6
> > System based on Renesas Yocto 2.19.0 BSP [1]
> > Linux kernel 4.9
> > 
> > * Guest operating systems:
> > The same system as dom0.
> > 
> > * Functionality tested:
> > xl create/restart/shutdown
> > Guest domain reboot from its console
> > PV NET (nfsroot in domU) , PV Block (copy from xvda to nfsroot in DomU)
> > 
> > * Comments:
> > 
> > On DomU startup messages like following appeared:
> > 
> >     root@salvator-x-domx:~# (XEN) printk: 9 messages suppressed.
> >     (XEN) d1v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> >     (XEN) d1v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> >     (XEN) d1v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> >     (XEN) d1v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> 
> The vGIC emulation does not emulate I*ACTIVER* registers so far. But Linux
> only accesses them at boot to ensure the firmware didn't leave interrupt in
> active state. They are harmless for now.
> 
> >     [   65.333062] xen-blkback: backend/vbd/1/51713: using 4 queues,
> > protocol 1 (arm-abi) persistent grants
> >     [   65.357846] xen-blkback: backend/vbd/1/51714: using 4 queues,
> > protocol 1 (arm-abi) persistent grants
> >     [   65.514054] vif vif-1-0 vif1.0: Guest Rx ready
> >     [   65.518485] IPv6: ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes
> > ready
> >     [   65.525021] xenbr0: port 2(vif1.0) entered blocking state
> >     [   65.530359] xenbr0: port 2(vif1.0) entered forwarding state
> >     [   65.815976] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x0000000000063772 -> mfn=0x000000000072abb0: pfn=0x0000000000063772
> > -> mfn=0x0000000000727aad already exists
> >     [   65.834442] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x000000000006374e -> mfn=0x000000000072abb0: pfn=0x000000000006374e
> > -> mfn=0x0000000000727aad already exists
> >     [   66.025979] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x000000000006379c -> mfn=0x000000000072abb3: pfn=0x000000000006379c
> > -> mfn=0x000000000072abb1 already exists
> >     [   66.273534] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x0000000000063731 -> mfn=0x0000000000727c3d: pfn=0x0000000000063731
> > -> mfn=0x0000000000727c3e already exists
> >     [   66.328245] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x00000000000637ee -> mfn=0x0000000000727c3f: pfn=0x00000000000637ee
> > -> mfn=0x0000000000727c3d already exists
> 
> I was expecting Stefano to answer here as he knows better than me this part of
> the code.
> 
> Linux is storing the conversion between pfn (guest frame number) to the mfn
> (machine frame number) in an RB-tree. This will be used by the swiotlb code to
> know if a buffer is contiguous in the physical RAM.
> 
> In your case, the log says that there was already a mapping pfn <-> mfn in the
> tree. It looks to me the previous mapping has not been removed correctly.
> 
> Are you able to reproduce this reliably? If so, can you try to figure out who
> added the first mapping pfn <-> mfn?

Sorry, I skimmed over the email and missed those warnings.

Julien, you are correct. The mappings are added by
set_foreign_p2m_mapping, which is called on gnttab_map_refs, and should
be removed by clear_foreign_p2m_mapping, called by gnttab_unmap_refs.

Maybe the mapping function is called twice or the unmapping function is
not called when it should?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2017-05-23 17:03 Andrii Anisov
  2017-05-23 20:14 ` Stefano Stabellini
@ 2017-05-25 10:17 ` Julien Grall
  2017-05-25 18:41   ` Stefano Stabellini
  1 sibling, 1 reply; 28+ messages in thread
From: Julien Grall @ 2017-05-25 10:17 UTC (permalink / raw)
  To: Andrii Anisov, Xen Devel; +Cc: Stefano Stabellini

Hi Andrii,

On 23/05/17 18:03, Andrii Anisov wrote:
> * Hardware:
> Salvator-X board with Renesas R-Car H3 SoC (ARM64)
>
> * Software:
> XEN 4.9-rc6
> System based on Renesas Yocto 2.19.0 BSP [1]
> Linux kernel 4.9
>
> * Guest operating systems:
> The same system as dom0.
>
> * Functionality tested:
> xl create/restart/shutdown
> Guest domain reboot from its console
> PV NET (nfsroot in domU) , PV Block (copy from xvda to nfsroot in DomU)
>
> * Comments:
>
> On DomU startup messages like following appeared:
>
>     root@salvator-x-domx:~# (XEN) printk: 9 messages suppressed.
>     (XEN) d1v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
>     (XEN) d1v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
>     (XEN) d1v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
>     (XEN) d1v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0

The vGIC emulation does not emulate I*ACTIVER* registers so far. But 
Linux only accesses them at boot to ensure the firmware didn't leave 
interrupt in active state. They are harmless for now.

>     [   65.333062] xen-blkback: backend/vbd/1/51713: using 4 queues,
> protocol 1 (arm-abi) persistent grants
>     [   65.357846] xen-blkback: backend/vbd/1/51714: using 4 queues,
> protocol 1 (arm-abi) persistent grants
>     [   65.514054] vif vif-1-0 vif1.0: Guest Rx ready
>     [   65.518485] IPv6: ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes
> ready
>     [   65.525021] xenbr0: port 2(vif1.0) entered blocking state
>     [   65.530359] xenbr0: port 2(vif1.0) entered forwarding state
>     [   65.815976] xen_add_phys_to_mach_entry: cannot add
> pfn=0x0000000000063772 -> mfn=0x000000000072abb0: pfn=0x0000000000063772
> -> mfn=0x0000000000727aad already exists
>     [   65.834442] xen_add_phys_to_mach_entry: cannot add
> pfn=0x000000000006374e -> mfn=0x000000000072abb0: pfn=0x000000000006374e
> -> mfn=0x0000000000727aad already exists
>     [   66.025979] xen_add_phys_to_mach_entry: cannot add
> pfn=0x000000000006379c -> mfn=0x000000000072abb3: pfn=0x000000000006379c
> -> mfn=0x000000000072abb1 already exists
>     [   66.273534] xen_add_phys_to_mach_entry: cannot add
> pfn=0x0000000000063731 -> mfn=0x0000000000727c3d: pfn=0x0000000000063731
> -> mfn=0x0000000000727c3e already exists
>     [   66.328245] xen_add_phys_to_mach_entry: cannot add
> pfn=0x00000000000637ee -> mfn=0x0000000000727c3f: pfn=0x00000000000637ee
> -> mfn=0x0000000000727c3d already exists

I was expecting Stefano to answer here as he knows better than me this 
part of the code.

Linux is storing the conversion between pfn (guest frame number) to the 
mfn (machine frame number) in an RB-tree. This will be used by the 
swiotlb code to know if a buffer is contiguous in the physical RAM.

In your case, the log says that there was already a mapping pfn <-> mfn 
in the tree. It looks to me the previous mapping has not been removed 
correctly.

Are you able to reproduce this reliably? If so, can you try to figure 
out who added the first mapping pfn <-> mfn?

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2017-05-23 17:03 Andrii Anisov
@ 2017-05-23 20:14 ` Stefano Stabellini
  2017-05-25 10:17 ` Julien Grall
  1 sibling, 0 replies; 28+ messages in thread
From: Stefano Stabellini @ 2017-05-23 20:14 UTC (permalink / raw)
  To: Andrii Anisov; +Cc: Julien Grall, Stefano Stabellini, Xen Devel

On Tue, 23 May 2017, Andrii Anisov wrote:
> Raisin is not functional as described [2]:
> 
>     root@salvator-x-domx:/raisin# ./raise test
>     No config file found, copying default config
>     [raisin] I don't know distro unknown. It might be missing packages.
>     [raisin] I don't know distro unknown. It might be missing packages.
>     [raisin] I don't know distro unknown. Cannot install packages.
> 
> [1] http://elinux.org/R-Car/Boards/Yocto-Gen3
> [2] https://wiki.xenproject.org/wiki/Xen_ARM_Manual_Smoke_Test

Hi Andrii,

thanks for testing! I have just run `raise test` on ARM64 to double
check: it works OK as long as it can recognize the distro and find the
host kernel and initrd appropriately (for example, as I was using a
custom built xen and dom0 kernel I had to use the appended patch).

In your case the problem is that you are using yocto and basically there
is no yocto support in raisin at the moment: it cannot recognize it as a
distro, therefore it cannot figure out if bridge-utils is already
installed for example. It would be nice to have yocto support for it
though, I don't think it would be hard to come up with a patch and it
gives you a very quick way to do testing! ;-)


diff --git a/lib/common-tests.sh b/lib/common-tests.sh
index c07bb18..80b61d5 100644
--- a/lib/common-tests.sh
+++ b/lib/common-tests.sh
@@ -163,20 +163,11 @@ function check_guest_alive() {
 }
 
 function get_host_kernel() {
-    echo "/boot/vmlinuz-`uname -r`"
+    echo "/boot/kernel"
 }
 
 function get_host_initrd() {
-    if [[ $DISTRO = "Debian" ]]
-    then
-        echo "/boot/initrd.img-`uname -r`"
-    elif [[ $DISTRO = "Fedora" ]]
-    then
-        echo "/boot/initramfs-`uname -r`".img
-    else
-        echo "$PREPEND I don't know how to find the initrd" >&2
-        exit 1
-    fi
+    echo ""
 }
 
 function cirros_network_init() {


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply related	[flat|nested] 28+ messages in thread

* [TESTDAY] Test report
@ 2017-05-23 17:03 Andrii Anisov
  2017-05-23 20:14 ` Stefano Stabellini
  2017-05-25 10:17 ` Julien Grall
  0 siblings, 2 replies; 28+ messages in thread
From: Andrii Anisov @ 2017-05-23 17:03 UTC (permalink / raw)
  To: Xen Devel; +Cc: Julien Grall, Stefano Stabellini

* Hardware:
Salvator-X board with Renesas R-Car H3 SoC (ARM64)

* Software:
XEN 4.9-rc6
System based on Renesas Yocto 2.19.0 BSP [1]
Linux kernel 4.9

* Guest operating systems:
The same system as dom0.

* Functionality tested:
xl create/restart/shutdown
Guest domain reboot from its console
PV NET (nfsroot in domU) , PV Block (copy from xvda to nfsroot in DomU)

* Comments:

On DomU startup messages like following appeared:

     root@salvator-x-domx:~# (XEN) printk: 9 messages suppressed.
     (XEN) d1v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
     (XEN) d1v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
     (XEN) d1v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
     (XEN) d1v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0
     [   65.333062] xen-blkback: backend/vbd/1/51713: using 4 queues, 
protocol 1 (arm-abi) persistent grants
     [   65.357846] xen-blkback: backend/vbd/1/51714: using 4 queues, 
protocol 1 (arm-abi) persistent grants
     [   65.514054] vif vif-1-0 vif1.0: Guest Rx ready
     [   65.518485] IPv6: ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes 
ready
     [   65.525021] xenbr0: port 2(vif1.0) entered blocking state
     [   65.530359] xenbr0: port 2(vif1.0) entered forwarding state
     [   65.815976] xen_add_phys_to_mach_entry: cannot add 
pfn=0x0000000000063772 -> mfn=0x000000000072abb0: pfn=0x0000000000063772 
-> mfn=0x0000000000727aad already exists
     [   65.834442] xen_add_phys_to_mach_entry: cannot add 
pfn=0x000000000006374e -> mfn=0x000000000072abb0: pfn=0x000000000006374e 
-> mfn=0x0000000000727aad already exists
     [   66.025979] xen_add_phys_to_mach_entry: cannot add 
pfn=0x000000000006379c -> mfn=0x000000000072abb3: pfn=0x000000000006379c 
-> mfn=0x000000000072abb1 already exists
     [   66.273534] xen_add_phys_to_mach_entry: cannot add 
pfn=0x0000000000063731 -> mfn=0x0000000000727c3d: pfn=0x0000000000063731 
-> mfn=0x0000000000727c3e already exists
     [   66.328245] xen_add_phys_to_mach_entry: cannot add 
pfn=0x00000000000637ee -> mfn=0x0000000000727c3f: pfn=0x00000000000637ee 
-> mfn=0x0000000000727c3d already exists

     root@salvator-x-domx:

Raisin is not functional as described [2]:

     root@salvator-x-domx:/raisin# ./raise test
     No config file found, copying default config
     [raisin] I don't know distro unknown. It might be missing packages.
     [raisin] I don't know distro unknown. It might be missing packages.
     [raisin] I don't know distro unknown. Cannot install packages.

[1] http://elinux.org/R-Car/Boards/Yocto-Gen3
[2] https://wiki.xenproject.org/wiki/Xen_ARM_Manual_Smoke_Test

-- 

*Andrii Anisov*



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* [TESTDAY] Test report
@ 2016-05-13 15:14 Tamas K Lengyel
  0 siblings, 0 replies; 28+ messages in thread
From: Tamas K Lengyel @ 2016-05-13 15:14 UTC (permalink / raw)
  To: Xen-devel

* Hardware: Intel(R) Xeon(R) CPU E5-2430
* Sofware: Debian Jessie dom0
* Functionality tested:
xl save/resume
vm_event/mem_access/monitor/altp2m

Comment: everything works as expected.

Cheers,
Tamas

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2015-10-01 16:59 Tamas K Lengyel
@ 2015-10-01 17:04 ` Wei Liu
  0 siblings, 0 replies; 28+ messages in thread
From: Wei Liu @ 2015-10-01 17:04 UTC (permalink / raw)
  To: Tamas K Lengyel; +Cc: wei.liu2, Xen-devel

On Thu, Oct 01, 2015 at 10:59:05AM -0600, Tamas K Lengyel wrote:
> * Hardware:
> 
> Intel(R) Core(TM) i7-2600 CPU, DQ67SW motherboard
> 
> * Software:
> 
> Xen 4.6 rc4, Ubuntu 14.04 LTS, Kernel 4.2 with all Xen modules built-in
> 
> * Guest operating systems:
> 
> Windows 7 SP1 x86 and x64, Ubuntu 14.04, Ubuntu 15.04
> 
> * Functionality tested:
> 
> xl save/restore
> pvgrub2
> VT-d device pass-through (rdm_policy=relaxed is now required for some
> devices)
> XSM with secondary control domain
> VM event subsystem on x86: mem_access, int3, cr events
> Mem_sharing
> 

Wow, this is quite a few test cases.

> * Comments:
> 
> Everything works as expected.

Great! Thank you for your report!

Wei.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* [TESTDAY] Test report
@ 2015-10-01 16:59 Tamas K Lengyel
  2015-10-01 17:04 ` Wei Liu
  0 siblings, 1 reply; 28+ messages in thread
From: Tamas K Lengyel @ 2015-10-01 16:59 UTC (permalink / raw)
  To: Xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 506 bytes --]

* Hardware:

Intel(R) Core(TM) i7-2600 CPU, DQ67SW motherboard

* Software:

Xen 4.6 rc4, Ubuntu 14.04 LTS, Kernel 4.2 with all Xen modules built-in

* Guest operating systems:

Windows 7 SP1 x86 and x64, Ubuntu 14.04, Ubuntu 15.04

* Functionality tested:

xl save/restore
pvgrub2
VT-d device pass-through (rdm_policy=relaxed is now required for some
devices)
XSM with secondary control domain
VM event subsystem on x86: mem_access, int3, cr events
Mem_sharing

* Comments:

Everything works as expected.

[-- Attachment #1.2: Type: text/html, Size: 599 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-10-30 14:39 ` Ian Campbell
@ 2014-10-31  6:35   ` Jan Vejvalka
  0 siblings, 0 replies; 28+ messages in thread
From: Jan Vejvalka @ 2014-10-31  6:35 UTC (permalink / raw)
  To: Ian Campbell; +Cc: roger.pau, xen-devel

Hi Ian and Roger,

    thank you for your help.

On 30.10.2014 15:39, Ian Campbell wrote:
> On Thu, 2014-10-30 at 11:54 +0100, Jan Vejvalka wrote:
>> Won't boot windows over iSCSI (not new in 4.5), says in
>> /var/log/xen/qemu-dm-example.hvm.log
>> qemu-system-i386: -drive
>> file=portal=(IP):3260,iqn=(iqn),w,if=ide,index=0,media=disk,format=raw,cache=writeback:
>> could not open disk image portal=(IP):3260: Unknown protocol
>
> What xl.cfg syntax did you use for this disk?
>
> I'm not seeing the file=portal=(IP):3260 syntax in the qemu manpage,
> where did it come from?

This is what I have in PV guest config (and it works fine):
disk = [ 
'script=block-iscsi,vdev=xvda1,target=portal=(IP):3260,iqn=(iqn),w' ]
... so I put the same in the HVM guest config (just substituting hda for 
xvda1).
If I use iscsiadm to map the iscsi drive locally and then I put
disk = [ 'phy:/dev/sdf,hda,w' ]
in my guest config, it works.

> One of the examples given in the qemu docs is:
>          -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
> which I would expect to correspond to an xl.cfg disk spec line which
> ends:
>          target=file=iscsi://192.0.2.1/iqn.2001-04.com.example/1

Sorry to ask further... how should it begin ?
I tried several variants, e.g.
disk = [ 'vdev=hda,target=file=iscsi://(IP):3260/(iqn)' ], but then
I get
libxl: error: libxl_device.c:283:libxl__device_disk_set_backend: Disk 
vdev=hda failed to stat: file=iscsi://(IP):3260/(iqn): No such file or 
directory.


On 30.10.2014 15:58, Roger Pau Monné wrote:
 > If you want to use iSCSI disks with an HVM domain you should use a
 > stubdomain. Adding the following to your config file should solve it:
 >
 > device_model_stubdomain_override=1

Did not. Using that and the 'original'
disk = [ 'script=block-iscsi,vdev=hda,target=portal=(IP):3260,iqn=(iqn),w'],
I get

Parsing config from xen/w7c.xenconf
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: 
/etc/xen/scripts/block-iscsi add [-1] exited with error status 1
libxl: error: libxl_device.c:1078:device_hotplug_child_death_cb: script: 
Device already opened
libxl: error: libxl_dm.c:1118:spawn_stub_launch_dm: error connecting 
disk devices
libxl: error: libxl_dm.c:1233:stubdom_pvqemu_cb: error connecting nics 
devices: Interrupted system call

on the console and

Waiting for domain example.hvm (domid 30) to die [pid 6556]
Domain 30 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 30 needs to be cleaned up: destroying the domain
libxl: error: libxl.c:1542:libxl__destroy_domid: non-existant domain 31
libxl: error: libxl.c:1480:stubdom_destroy_callback: unable to destroy 
stubdom with domid 31
libxl: error: libxl_aoutils.c:464:async_exec_timeout: killing execution 
of /etc/xen/scripts/block-iscsi remove because of timeout
libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: 
/etc/xen/scripts/block-iscsi remove [-1] died due to fatal signal Killed
libxl: error: libxl.c:1433:domain_destroy_cb: destruction of domain 30 
failed
Done. Exiting now

in /var/log/xen/xl-example.hvm.log.

Grateful for any further advice,

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-10-30 10:54 Jan Vejvalka
  2014-10-30 14:39 ` Ian Campbell
@ 2014-10-30 14:58 ` Roger Pau Monné
  1 sibling, 0 replies; 28+ messages in thread
From: Roger Pau Monné @ 2014-10-30 14:58 UTC (permalink / raw)
  To: Jan Vejvalka, xen-devel

El 30/10/14 a les 11.54, Jan Vejvalka ha escrit:
> * Hardware:
> Supermicro X6D, X8D (Intel dual Xeon machines)
> 
> * Software:
> Slackware 14.1, Dom0 3.16.3, 3.17.1
> 
> * Guest operating systems:
> Slackware 14.1, DomU 3.17.1
> Windows 7
> 
> * Functionality tested:
> iSCSI
> 
> * Comments:
> Won't boot windows over iSCSI (not new in 4.5), says in
> /var/log/xen/qemu-dm-example.hvm.log
> qemu-system-i386: -drive
> file=portal=(IP):3260,iqn=(iqn),w,if=ide,index=0,media=disk,format=raw,cache=writeback:
> could not open disk image portal=(IP):3260: Unknown protocol
> 
> Other than that, great work!

Hello,

If you want to use iSCSI disks with an HVM domain you should use a
stubdomain. Adding the following to your config file should solve it:

device_model_stubdomain_override=1

Roger.

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-10-30 10:54 Jan Vejvalka
@ 2014-10-30 14:39 ` Ian Campbell
  2014-10-31  6:35   ` Jan Vejvalka
  2014-10-30 14:58 ` Roger Pau Monné
  1 sibling, 1 reply; 28+ messages in thread
From: Ian Campbell @ 2014-10-30 14:39 UTC (permalink / raw)
  To: Jan Vejvalka; +Cc: xen-devel

On Thu, 2014-10-30 at 11:54 +0100, Jan Vejvalka wrote:
> Won't boot windows over iSCSI (not new in 4.5), says in 
> /var/log/xen/qemu-dm-example.hvm.log
> qemu-system-i386: -drive 
> file=portal=(IP):3260,iqn=(iqn),w,if=ide,index=0,media=disk,format=raw,cache=writeback: 
> could not open disk image portal=(IP):3260: Unknown protocol

What xl.cfg syntax did you use for this disk?

I'm not seeing the file=portal=(IP):3260 syntax in the qemu manpage,
where did it come from?

One of the examples given in the qemu docs is:
        -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
which I would expect to correspond to an xl.cfg disk spec line which
ends:
        target=file=iscsi://192.0.2.1/iqn.2001-04.com.example/1

Ian.

^ permalink raw reply	[flat|nested] 28+ messages in thread

* [TESTDAY] Test report
@ 2014-10-30 10:54 Jan Vejvalka
  2014-10-30 14:39 ` Ian Campbell
  2014-10-30 14:58 ` Roger Pau Monné
  0 siblings, 2 replies; 28+ messages in thread
From: Jan Vejvalka @ 2014-10-30 10:54 UTC (permalink / raw)
  To: xen-devel

* Hardware:
Supermicro X6D, X8D (Intel dual Xeon machines)

* Software:
Slackware 14.1, Dom0 3.16.3, 3.17.1

* Guest operating systems:
Slackware 14.1, DomU 3.17.1
Windows 7

* Functionality tested:
iSCSI

* Comments:
Won't boot windows over iSCSI (not new in 4.5), says in 
/var/log/xen/qemu-dm-example.hvm.log
qemu-system-i386: -drive 
file=portal=(IP):3260,iqn=(iqn),w,if=ide,index=0,media=disk,format=raw,cache=writeback: 
could not open disk image portal=(IP):3260: Unknown protocol

Other than that, great work!

Thanks :-)

Jan

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-24 19:06         ` Don Slutz
  2014-01-24 19:20           ` Konrad Rzeszutek Wilk
@ 2014-01-27  1:15           ` herbert cland
  1 sibling, 0 replies; 28+ messages in thread
From: herbert cland @ 2014-01-27  1:15 UTC (permalink / raw)
  To: Don Slutz; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 3960 bytes --]

This a boring BUG which has a  long history,  from xen 3.* ~ 4.4rc2, which is always occurred when guest os is centos 6+,   as i know.
But it is very strange that only a few guys mention  it and care it.
please read following links:
http://lists.xen.org/archives/html/xen-devel/2013-08/msg01315.html 
http://xen.1045712.n5.nabble.com/xm-save-checkpoint-problem-td2519789.html 


  




herbert cland

From: Don Slutz
Date: 2014-01-25 03:06
To: Konrad Rzeszutek Wilk; Don Slutz
CC: xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [TESTDAY] Test report
On 01/24/14 11:43, Don Slutz wrote:

On 01/24/14 09:58, Konrad Rzeszutek Wilk wrote:

On Thu, Jan 23, 2014 at 05:03:39PM -0500, Don Slutz wrote:

On 01/20/14 18:35, Konrad Rzeszutek Wilk wrote:

Don Slutz <dslutz@verizon.com> wrote:

[snip]


WARNING: g.e. still in use!
WARNING: g.e. still in use!
WARNING: g.e. still in use!
pm_op(): platform_pm_resume+0x0/0x50 returns -19
PM: Device i8042 failed to resume: error -19
INFO: task sadc:22164 blocked for more then 120 seconds.
"echo 0 >..."
INFO: task sadc:22164 blocked for more then 120 seconds.

[root@dcs-xen-54 ~]# xl des 17
[root@dcs-xen-54 ~]# xl restore -V
/big/xl-save/centos-6.4-x86_64.0.save


Not sure if this is expected or not.

I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect. Did it work if you used xend (you might have to configure it be enabled)?

I have not used xend/xe in a long time.  I did need to configure it.

Does not start:


# /etc/init.d/xend start
WARNING: Enabling the xend toolstack.
xend is deprecated and scheduled for removal. Please migrate
to another toolstack ASAP.
Traceback (most recent call last):
  File "/usr/sbin/xend", line 110, in <module>
    sys.exit(main())
  File "/usr/sbin/xend", line 91, in main
    start_blktapctrl()
  File "/usr/sbin/xend", line 77, in start_blktapctrl
    start_daemon("blktapctrl", "")
  File "/usr/sbin/xend", line 74, in start_daemon
    os.execvp(daemon, (daemon,) + args)
  File "/usr/lib64/python2.7/os.py", line 344, in execvp
    _execvpe(file, args)
  File "/usr/lib64/python2.7/os.py", line 380, in _execvpe
    func(fullname, *argrest)
OSError: [Errno 2] No such file or directory


How important is it to try this?

It tells us whether the issue is indeed with the 'fast-cancel' thing.

But, I do recall seeing a patch from Ian Jackson for this - I just
don't remember what it was called - it was posted here and perhaps
applying it would help?


I have not found a patch.  The bug #30:


http://bugs.xenproject.org/xen/bug/30

Looks to me like the issue I am seeing.  The Guest I was testing this on is an old kernel (as far as this bug) and so I would expect it might be related.


Here is what I see that may link it to this:


From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [Xen-devel] 3.4.70+ kernel WARNING spew dysfunction on failed migration
Date: Fri, 10 Jan 2014 10:26:31 +0000


...

Looks like RHEL4 (linux-2.6.9-89.0.16.EL kernel) doesn't have the
support for the new mode at all.

It would probably be wise to validate this under xend before chasing
red-herrings with xl.

Ian.


So I will continue the fight to get xend running.

   -Don




Ah, now have xend running, but still need to convert from an xl.cfg file to a xmdomain.cfg...  Having not used xm in years, this will take a while.  The man page does not say how to build an hvm guest.

I did another test and Fedora 19 (x86_64) saved just fine.  So this looks to be bug #30.

If I understand this all, this means that the older linux kernels will fail this way also if a migrate fails and the source guest is restarted.

So, do I continue to get xend working, or just say it is an example of bug #30?

    -Don Slutz







    -Don Slutz

[-- Attachment #1.2: Type: text/html, Size: 7730 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-24 19:06         ` Don Slutz
@ 2014-01-24 19:20           ` Konrad Rzeszutek Wilk
  2014-01-27  1:15           ` herbert cland
  1 sibling, 0 replies; 28+ messages in thread
From: Konrad Rzeszutek Wilk @ 2014-01-24 19:20 UTC (permalink / raw)
  To: Don Slutz; +Cc: xen-devel

> >So I will continue the fight to get xend running.
> >
> >   -Don
> >
> >
> 
> Ah, now have xend running, but still need to convert from an xl.cfg file to a xmdomain.cfg...  Having not used xm in years, this will take a while.  The man page does not say how to build an hvm guest.
> 
> I did another test and Fedora 19 (x86_64) saved just fine.  So this looks to be bug #30.
> 
> If I understand this all, this means that the older linux kernels will fail this way also if a migrate fails and the source guest is restarted.
> 
> So, do I continue to get xend working, or just say it is an example of bug #30?

Blame #30 :-)

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-24 16:43       ` Don Slutz
@ 2014-01-24 19:06         ` Don Slutz
  2014-01-24 19:20           ` Konrad Rzeszutek Wilk
  2014-01-27  1:15           ` herbert cland
  0 siblings, 2 replies; 28+ messages in thread
From: Don Slutz @ 2014-01-24 19:06 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk, Don Slutz; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 3609 bytes --]

On 01/24/14 11:43, Don Slutz wrote:
> On 01/24/14 09:58, Konrad Rzeszutek Wilk wrote:
>> On Thu, Jan 23, 2014 at 05:03:39PM -0500, Don Slutz wrote:
>>> On 01/20/14 18:35, Konrad Rzeszutek Wilk wrote:
>>>> Don Slutz<dslutz@verizon.com>  wrote:
>>> [snip]
>>>
>>>>> WARNING: g.e. still in use!
>>>>> WARNING: g.e. still in use!
>>>>> WARNING: g.e. still in use!
>>>>> pm_op(): platform_pm_resume+0x0/0x50 returns -19
>>>>> PM: Device i8042 failed to resume: error -19
>>>>> INFO: task sadc:22164 blocked for more then 120 seconds.
>>>>> "echo 0 >..."
>>>>> INFO: task sadc:22164 blocked for more then 120 seconds.
>>>>>
>>>>> [root@dcs-xen-54 ~]# xl des 17
>>>>> [root@dcs-xen-54 ~]# xl restore -V
>>>>> /big/xl-save/centos-6.4-x86_64.0.save
>>>>>
>>>>>
>>>>> Not sure if this is expected or not.
>>>> I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect. Did it work if you used xend (you might have to configure it be enabled)?
>>> I have not used xend/xe in a long time.  I did need to configure it.
>>>
>>> Does not start:
>>>
>>>
>>> # /etc/init.d/xend start
>>> WARNING: Enabling the xend toolstack.
>>> xend is deprecated and scheduled for removal. Please migrate
>>> to another toolstack ASAP.
>>> Traceback (most recent call last):
>>>    File "/usr/sbin/xend", line 110, in <module>
>>>      sys.exit(main())
>>>    File "/usr/sbin/xend", line 91, in main
>>>      start_blktapctrl()
>>>    File "/usr/sbin/xend", line 77, in start_blktapctrl
>>>      start_daemon("blktapctrl", "")
>>>    File "/usr/sbin/xend", line 74, in start_daemon
>>>      os.execvp(daemon, (daemon,) + args)
>>>    File "/usr/lib64/python2.7/os.py", line 344, in execvp
>>>      _execvpe(file, args)
>>>    File "/usr/lib64/python2.7/os.py", line 380, in _execvpe
>>>      func(fullname, *argrest)
>>> OSError: [Errno 2] No such file or directory
>>>
>>>
>>> How important is it to try this?
>> It tells us whether the issue is indeed with the 'fast-cancel' thing.
>>
>> But, I do recall seeing a patch from Ian Jackson for this - I just
>> don't remember what it was called - it was posted here and perhaps
>> applying it would help?
>
> I have not found a patch.  The bug #30:
>
>
> http://bugs.xenproject.org/xen/bug/30
>
> Looks to me like the issue I am seeing.  The Guest I was testing this on is an old kernel (as far as this bug) and so I would expect it might be related.
>
>
> Here is what I see that may link it to this:
>
>     *From*: Ian Campbell<Ian.Campbell@citrix.com>
>     *To*: Ian Jackson<Ian.Jackson@eu.citrix.com>
>     *Cc*:xen-devel@lists.xen.org
>     *Subject*: Re: [Xen-devel] 3.4.70+ kernel WARNING spew dysfunction on failed migration
>     *Date*: Fri, 10 Jan 2014 10:26:31 +0000
>
> ...
>
>     Looks like RHEL4 (linux-2.6.9-89.0.16.EL kernel) doesn't have the
>     support for the new mode at all.
>
>     It would probably be wise to validate this under xend before chasing
>     red-herrings with xl.
>
>     Ian.
>
>
> So I will continue the fight to get xend running.
>
>    -Don
>
>

Ah, now have xend running, but still need to convert from an xl.cfg file to a xmdomain.cfg...  Having not used xm in years, this will take a while.  The man page does not say how to build an hvm guest.

I did another test and Fedora 19 (x86_64) saved just fine.  So this looks to be bug #30.

If I understand this all, this means that the older linux kernels will fail this way also if a migrate fails and the source guest is restarted.

So, do I continue to get xend working, or just say it is an example of bug #30?

     -Don Slutz


>
>
>
>>>      -Don Slutz
>>>
>


[-- Attachment #1.2: Type: text/html, Size: 5737 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-24 14:58     ` Konrad Rzeszutek Wilk
@ 2014-01-24 16:43       ` Don Slutz
  2014-01-24 19:06         ` Don Slutz
  0 siblings, 1 reply; 28+ messages in thread
From: Don Slutz @ 2014-01-24 16:43 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk, Don Slutz; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 2928 bytes --]

On 01/24/14 09:58, Konrad Rzeszutek Wilk wrote:
> On Thu, Jan 23, 2014 at 05:03:39PM -0500, Don Slutz wrote:
>> On 01/20/14 18:35, Konrad Rzeszutek Wilk wrote:
>>> Don Slutz <dslutz@verizon.com> wrote:
>> [snip]
>>
>>>> WARNING: g.e. still in use!
>>>> WARNING: g.e. still in use!
>>>> WARNING: g.e. still in use!
>>>> pm_op(): platform_pm_resume+0x0/0x50 returns -19
>>>> PM: Device i8042 failed to resume: error -19
>>>> INFO: task sadc:22164 blocked for more then 120 seconds.
>>>> "echo 0 >..."
>>>> INFO: task sadc:22164 blocked for more then 120 seconds.
>>>>
>>>> [root@dcs-xen-54 ~]# xl des 17
>>>> [root@dcs-xen-54 ~]# xl restore -V
>>>> /big/xl-save/centos-6.4-x86_64.0.save
>>>>
>>>>
>>>> Not sure if this is expected or not.
>>> I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect. Did it work if you used xend (you might have to configure it be enabled)?
>> I have not used xend/xe in a long time.  I did need to configure it.
>>
>> Does not start:
>>
>>
>> # /etc/init.d/xend start
>> WARNING: Enabling the xend toolstack.
>> xend is deprecated and scheduled for removal. Please migrate
>> to another toolstack ASAP.
>> Traceback (most recent call last):
>>    File "/usr/sbin/xend", line 110, in <module>
>>      sys.exit(main())
>>    File "/usr/sbin/xend", line 91, in main
>>      start_blktapctrl()
>>    File "/usr/sbin/xend", line 77, in start_blktapctrl
>>      start_daemon("blktapctrl", "")
>>    File "/usr/sbin/xend", line 74, in start_daemon
>>      os.execvp(daemon, (daemon,) + args)
>>    File "/usr/lib64/python2.7/os.py", line 344, in execvp
>>      _execvpe(file, args)
>>    File "/usr/lib64/python2.7/os.py", line 380, in _execvpe
>>      func(fullname, *argrest)
>> OSError: [Errno 2] No such file or directory
>>
>>
>> How important is it to try this?
> It tells us whether the issue is indeed with the 'fast-cancel' thing.
>
> But, I do recall seeing a patch from Ian Jackson for this - I just
> don't remember what it was called - it was posted here and perhaps
> applying it would help?

I have not found a patch.  The bug #30:


http://bugs.xenproject.org/xen/bug/30

Looks to me like the issue I am seeing.  The Guest I was testing this on is an old kernel (as far as this bug) and so I would expect it might be related.


Here is what I see that may link it to this:

    *From*: Ian Campbell <Ian.Campbell@citrix.com>
    *To*: Ian Jackson <Ian.Jackson@eu.citrix.com>
    *Cc*: xen-devel@lists.xen.org
    *Subject*: Re: [Xen-devel] 3.4.70+ kernel WARNING spew dysfunction on failed migration
    *Date*: Fri, 10 Jan 2014 10:26:31 +0000

...

    Looks like RHEL4 (linux-2.6.9-89.0.16.EL kernel) doesn't have the
    support for the new mode at all.

    It would probably be wise to validate this under xend before chasing
    red-herrings with xl.

    Ian.


So I will continue the fight to get xend running.

    -Don





>>      -Don Slutz
>>


[-- Attachment #1.2: Type: text/html, Size: 4491 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-23 22:03   ` Don Slutz
@ 2014-01-24 14:58     ` Konrad Rzeszutek Wilk
  2014-01-24 16:43       ` Don Slutz
  0 siblings, 1 reply; 28+ messages in thread
From: Konrad Rzeszutek Wilk @ 2014-01-24 14:58 UTC (permalink / raw)
  To: Don Slutz; +Cc: xen-devel

On Thu, Jan 23, 2014 at 05:03:39PM -0500, Don Slutz wrote:
> On 01/20/14 18:35, Konrad Rzeszutek Wilk wrote:
> >Don Slutz <dslutz@verizon.com> wrote:
> 
> [snip]
> 
> >>WARNING: g.e. still in use!
> >>WARNING: g.e. still in use!
> >>WARNING: g.e. still in use!
> >>pm_op(): platform_pm_resume+0x0/0x50 returns -19
> >>PM: Device i8042 failed to resume: error -19
> >>INFO: task sadc:22164 blocked for more then 120 seconds.
> >>"echo 0 >..."
> >>INFO: task sadc:22164 blocked for more then 120 seconds.
> >>
> >>[root@dcs-xen-54 ~]# xl des 17
> >>[root@dcs-xen-54 ~]# xl restore -V
> >>/big/xl-save/centos-6.4-x86_64.0.save
> >>
> >>
> >>Not sure if this is expected or not.
> >I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect. Did it work if you used xend (you might have to configure it be enabled)?
> 
> I have not used xend/xe in a long time.  I did need to configure it.
> 
> Does not start:
> 
> 
> # /etc/init.d/xend start
> WARNING: Enabling the xend toolstack.
> xend is deprecated and scheduled for removal. Please migrate
> to another toolstack ASAP.
> Traceback (most recent call last):
>   File "/usr/sbin/xend", line 110, in <module>
>     sys.exit(main())
>   File "/usr/sbin/xend", line 91, in main
>     start_blktapctrl()
>   File "/usr/sbin/xend", line 77, in start_blktapctrl
>     start_daemon("blktapctrl", "")
>   File "/usr/sbin/xend", line 74, in start_daemon
>     os.execvp(daemon, (daemon,) + args)
>   File "/usr/lib64/python2.7/os.py", line 344, in execvp
>     _execvpe(file, args)
>   File "/usr/lib64/python2.7/os.py", line 380, in _execvpe
>     func(fullname, *argrest)
> OSError: [Errno 2] No such file or directory
> 
> 
> How important is it to try this?

It tells us whether the issue is indeed with the 'fast-cancel' thing.

But, I do recall seeing a patch from Ian Jackson for this - I just
don't remember what it was called - it was posted here and perhaps
applying it would help?

> 
>     -Don Slutz
> 

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-20 23:35 ` Konrad Rzeszutek Wilk
  2014-01-23 10:51   ` Ian Campbell
@ 2014-01-23 22:03   ` Don Slutz
  2014-01-24 14:58     ` Konrad Rzeszutek Wilk
  1 sibling, 1 reply; 28+ messages in thread
From: Don Slutz @ 2014-01-23 22:03 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk, Don Slutz, xen-devel

On 01/20/14 18:35, Konrad Rzeszutek Wilk wrote:
> Don Slutz <dslutz@verizon.com> wrote:

[snip]

>> WARNING: g.e. still in use!
>> WARNING: g.e. still in use!
>> WARNING: g.e. still in use!
>> pm_op(): platform_pm_resume+0x0/0x50 returns -19
>> PM: Device i8042 failed to resume: error -19
>> INFO: task sadc:22164 blocked for more then 120 seconds.
>> "echo 0 >..."
>> INFO: task sadc:22164 blocked for more then 120 seconds.
>>
>>   
>> [root@dcs-xen-54 ~]# xl des 17
>> [root@dcs-xen-54 ~]# xl restore -V
>> /big/xl-save/centos-6.4-x86_64.0.save
>>
>>
>> Not sure if this is expected or not.
> I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect. Did it work if you used xend (you might have to configure it be enabled)?

I have not used xend/xe in a long time.  I did need to configure it.

Does not start:


# /etc/init.d/xend start
WARNING: Enabling the xend toolstack.
xend is deprecated and scheduled for removal. Please migrate
to another toolstack ASAP.
Traceback (most recent call last):
   File "/usr/sbin/xend", line 110, in <module>
     sys.exit(main())
   File "/usr/sbin/xend", line 91, in main
     start_blktapctrl()
   File "/usr/sbin/xend", line 77, in start_blktapctrl
     start_daemon("blktapctrl", "")
   File "/usr/sbin/xend", line 74, in start_daemon
     os.execvp(daemon, (daemon,) + args)
   File "/usr/lib64/python2.7/os.py", line 344, in execvp
     _execvpe(file, args)
   File "/usr/lib64/python2.7/os.py", line 380, in _execvpe
     func(fullname, *argrest)
OSError: [Errno 2] No such file or directory


How important is it to try this?

     -Don Slutz

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-20 23:35 ` Konrad Rzeszutek Wilk
@ 2014-01-23 10:51   ` Ian Campbell
  2014-01-23 22:03   ` Don Slutz
  1 sibling, 0 replies; 28+ messages in thread
From: Ian Campbell @ 2014-01-23 10:51 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: Don Slutz, xen-devel

On Mon, 2014-01-20 at 18:35 -0500, Konrad Rzeszutek Wilk wrote:
> >[root@dcs-xen-54 ~]# xl save -p 6 /big/xl-save/centos-6.4-x86_64.0.save
> >Saving to /big/xl-save/centos-6.4-x86_64.0.save new xl format (info
> >0x0/0x0/560)
> >xc: Saving memory: iter 0 (last sent 0 skipped 0): 1044481/1044481 
> >100%
> >[root@dcs-xen-54 ~]# xl unpause 6
> >
> >has left domain #6 in a bad disk state (on VGA):
> >
> >INFO: task jbd2/dm-0-8:386 blocked for more then 120 seconds.
> >INFO: task sadc:22139 blocked for more then 120 seconds.
> >
> >
> >However "xl restore -V /big/xl-save/centos-6.4-x86_64.0.save" looks to
> >work fine.
> >
> >2nd time the unpause failed with:
> >[root@dcs-xen-54 ~]# xl unpause 17
> >
> >WARNING: g.e. still in use!
> >WARNING: g.e. still in use!
> >WARNING: g.e. still in use!
> >pm_op(): platform_pm_resume+0x0/0x50 returns -19
> >PM: Device i8042 failed to resume: error -19
> >INFO: task sadc:22164 blocked for more then 120 seconds.
> >"echo 0 >..."
> >INFO: task sadc:22164 blocked for more then 120 seconds.
> >
> >  
> >[root@dcs-xen-54 ~]# xl des 17
> >[root@dcs-xen-54 ~]# xl restore -V
> >/big/xl-save/centos-6.4-x86_64.0.save
> >
> >
> >Not sure if this is expected or not.
> 
> I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect.

It seems to me that it would be the same issue, but I can't recall if
the fix from Ian J was in rc2 or not.

Ian.

^ permalink raw reply	[flat|nested] 28+ messages in thread

* Re: [TESTDAY] Test report
  2014-01-20 22:49 Don Slutz
@ 2014-01-20 23:35 ` Konrad Rzeszutek Wilk
  2014-01-23 10:51   ` Ian Campbell
  2014-01-23 22:03   ` Don Slutz
  0 siblings, 2 replies; 28+ messages in thread
From: Konrad Rzeszutek Wilk @ 2014-01-20 23:35 UTC (permalink / raw)
  To: Don Slutz, xen-devel

Don Slutz <dslutz@verizon.com> wrote:
>* Hardware:
>
>SeaMicro*SM15000-XN*Quad Core Servers with Intel® Xeon® E3-1265Lv2
>processors (“Ivy Bridge” microarchitecture)
>
>1 server, 32G of memory.
>
>* Software:
>
>Fedora 17 (3.8.11-100.fc17.x86_64)
>CentOS release 5.10 (2.6.18-371.el5xen)
>
>* Guest operating systems:
>
>
>on Fedora 17: All HVM:
>
>
>vm:ubuntu-12.04.3-server-amd64
>Linux ubuntu 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
>16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>vm:centos-5.9-x86_64
>Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Tue Jan 8 18:35:04
>EST 2013 x86_64 x86_64 x86_64 GNU/Linux
>vm:debian-7.2.0-amd64
>Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
>vm:rhel-6.4-x86_64
>Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29
>11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
>vm:centos-6.4-i386
>Linux localhost.localdomain 2.6.32-358.el6.i686 #1 SMP Thu Feb 21
>21:50:49 UTC 2013 i686 i686 i386 GNU/Linux
>vm:centos-5.9-i386
>Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Tue Jan 8 19:22:56
>EST 2013 i686 i686 i386 GNU/Linux
>vm:rhel-5.9-i386
>Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Wed Nov 28
>22:04:26 EST 2012 i686 i686 i386 GNU/Linux
>vm:centos-6.4-x86_64
>Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22
>00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>vm:rhel-6.4-i386
>Linux localhost.localdomain 2.6.32-358.el6.i686 #1 SMP Tue Jan 29
>11:48:01 EST 2013 i686 i686 i386 GNU/Linux
>vm:rhel-5.9-x86_64
>Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Wed Nov 28
>21:31:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
>
>
>windows-server-2008-ENT-x86_64
>
>
>* Functionality tested:
>xl
>xl save
>xl restore
>
>
>* Comments:
>
>4.4.rc2 does not build on CentOS release 5.10:
>
>Need
>
>* 407a3c0 (origin/staging) compat/memory: fix build with old gcc
>
>and a newer upstream QEMU then qemu-xen-4.4.0-rc1
>
>* b97307e (HEAD, tag: qemu-xen-4.4.0-rc1, dummy) xen_disk: mark ioreq
>as mapped before unmapping in error case
>*   d84e452 Merge remote branch 'origin/stable-1.6' into
>xen-staging-master-9
>|\
>| * 62ecc3a (tag: v1.6.1) Update VERSION for 1.6.1 release
>
>
>Mail threads that are related:
>
>http://lists.xen.org/archives/html/xen-devel/2014-01/msg01477.html
>
>http://lists.xen.org/archives/html/xen-devel/2014-01/msg01520.html
>
>
>  
>[root@dcs-xen-54 ~]# xl save -p 6 /big/xl-save/centos-6.4-x86_64.0.save
>Saving to /big/xl-save/centos-6.4-x86_64.0.save new xl format (info
>0x0/0x0/560)
>xc: Saving memory: iter 0 (last sent 0 skipped 0): 1044481/1044481 
>100%
>[root@dcs-xen-54 ~]# xl unpause 6
>
>has left domain #6 in a bad disk state (on VGA):
>
>INFO: task jbd2/dm-0-8:386 blocked for more then 120 seconds.
>INFO: task sadc:22139 blocked for more then 120 seconds.
>
>
>However "xl restore -V /big/xl-save/centos-6.4-x86_64.0.save" looks to
>work fine.
>
>2nd time the unpause failed with:
>[root@dcs-xen-54 ~]# xl unpause 17
>
>WARNING: g.e. still in use!
>WARNING: g.e. still in use!
>WARNING: g.e. still in use!
>pm_op(): platform_pm_resume+0x0/0x50 returns -19
>PM: Device i8042 failed to resume: error -19
>INFO: task sadc:22164 blocked for more then 120 seconds.
>"echo 0 >..."
>INFO: task sadc:22164 blocked for more then 120 seconds.
>
>  
>[root@dcs-xen-54 ~]# xl des 17
>[root@dcs-xen-54 ~]# xl restore -V
>/big/xl-save/centos-6.4-x86_64.0.save
>
>
>Not sure if this is expected or not.

I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect. Did it work if you used xend (you might have to configure it be enabled)?

>
>    -Don Slutz
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xen.org
>http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 28+ messages in thread

* [TESTDAY] Test report
@ 2014-01-20 22:49 Don Slutz
  2014-01-20 23:35 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 28+ messages in thread
From: Don Slutz @ 2014-01-20 22:49 UTC (permalink / raw)
  To: xen-devel

* Hardware:

SeaMicro*SM15000-XN*Quad Core Servers with Intel® Xeon® E3-1265Lv2 processors (“Ivy Bridge” microarchitecture)

1 server, 32G of memory.

* Software:

Fedora 17 (3.8.11-100.fc17.x86_64)
CentOS release 5.10 (2.6.18-371.el5xen)

* Guest operating systems:


on Fedora 17: All HVM:


vm:ubuntu-12.04.3-server-amd64
Linux ubuntu 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
vm:centos-5.9-x86_64
Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Tue Jan 8 18:35:04 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
vm:debian-7.2.0-amd64
Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
vm:rhel-6.4-x86_64
Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
vm:centos-6.4-i386
Linux localhost.localdomain 2.6.32-358.el6.i686 #1 SMP Thu Feb 21 21:50:49 UTC 2013 i686 i686 i386 GNU/Linux
vm:centos-5.9-i386
Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Tue Jan 8 19:22:56 EST 2013 i686 i686 i386 GNU/Linux
vm:rhel-5.9-i386
Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Wed Nov 28 22:04:26 EST 2012 i686 i686 i386 GNU/Linux
vm:centos-6.4-x86_64
Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
vm:rhel-6.4-i386
Linux localhost.localdomain 2.6.32-358.el6.i686 #1 SMP Tue Jan 29 11:48:01 EST 2013 i686 i686 i386 GNU/Linux
vm:rhel-5.9-x86_64
Linux localhost.localdomain 2.6.18-348.el5xen #1 SMP Wed Nov 28 21:31:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux


windows-server-2008-ENT-x86_64


* Functionality tested:
xl
xl save
xl restore


* Comments:

4.4.rc2 does not build on CentOS release 5.10:

Need

* 407a3c0 (origin/staging) compat/memory: fix build with old gcc

and a newer upstream QEMU then qemu-xen-4.4.0-rc1

* b97307e (HEAD, tag: qemu-xen-4.4.0-rc1, dummy) xen_disk: mark ioreq as mapped before unmapping in error case
*   d84e452 Merge remote branch 'origin/stable-1.6' into xen-staging-master-9
|\
| * 62ecc3a (tag: v1.6.1) Update VERSION for 1.6.1 release


Mail threads that are related:

http://lists.xen.org/archives/html/xen-devel/2014-01/msg01477.html

http://lists.xen.org/archives/html/xen-devel/2014-01/msg01520.html


  
[root@dcs-xen-54 ~]# xl save -p 6 /big/xl-save/centos-6.4-x86_64.0.save
Saving to /big/xl-save/centos-6.4-x86_64.0.save new xl format (info 0x0/0x0/560)
xc: Saving memory: iter 0 (last sent 0 skipped 0): 1044481/1044481  100%
[root@dcs-xen-54 ~]# xl unpause 6

has left domain #6 in a bad disk state (on VGA):

INFO: task jbd2/dm-0-8:386 blocked for more then 120 seconds.
INFO: task sadc:22139 blocked for more then 120 seconds.


However "xl restore -V /big/xl-save/centos-6.4-x86_64.0.save" looks to work fine.

2nd time the unpause failed with:
[root@dcs-xen-54 ~]# xl unpause 17

WARNING: g.e. still in use!
WARNING: g.e. still in use!
WARNING: g.e. still in use!
pm_op(): platform_pm_resume+0x0/0x50 returns -19
PM: Device i8042 failed to resume: error -19
INFO: task sadc:22164 blocked for more then 120 seconds.
"echo 0 >..."
INFO: task sadc:22164 blocked for more then 120 seconds.

  
[root@dcs-xen-54 ~]# xl des 17
[root@dcs-xen-54 ~]# xl restore -V /big/xl-save/centos-6.4-x86_64.0.save


Not sure if this is expected or not.

    -Don Slutz

^ permalink raw reply	[flat|nested] 28+ messages in thread

* [TESTDAY] Test report
@ 2012-09-19  7:04 Dariusz Krempa
  0 siblings, 0 replies; 28+ messages in thread
From: Dariusz Krempa @ 2012-09-19  7:04 UTC (permalink / raw)
  To: xen-devel

Hi.
I'm newbie with Xen and event with linux, but almost 2 weeks i spend
on installation both on my box (thanks to Zhang Enming for his
tutorials) and finally i did it. VGA passthrough is possible on P8H67
even if in bios isn't option to turn on virtualisation.

* Hardware:
- CPU: i5 2400
- GTX 560 DirectCUII Top - drivers 275.50
- P8H67 with bios 3603
- 4GB ram :(

*Software:
- Ubuntu 12.04
- Dom0 kernel - 3.3-rc7
- DomU - windows xp sp3 - x86 (HVM pciback)
- Xen 4.2-rc4 with patch from David Gis

*Functionality
- Asus P8H67 + Asus GTX560OC = VGA passthrough

*Comments
In this moment i don't know that patch from David Gis is needed but i
used it. Dom0 , DomU Windows XP sp3. I'm newbie but i will try to
answer for questions about my configuration. Any suggestions will be
appreciated.

^ permalink raw reply	[flat|nested] 28+ messages in thread

end of thread, other threads:[~2017-05-25 18:41 UTC | newest]

Thread overview: 28+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-13 20:34 [TESTDAY] Test report Edgar E. Iglesias
2016-05-14 18:15 ` Julien Grall
2016-05-14 19:04   ` Edgar E. Iglesias
2016-05-16  9:58     ` Wei Liu
2016-05-16 13:20     ` Julien Grall
2016-05-16 13:41       ` Edgar E. Iglesias
2016-05-16 13:43         ` Julien Grall
  -- strict thread matches above, loose matches on Subject: below --
2017-05-23 17:03 Andrii Anisov
2017-05-23 20:14 ` Stefano Stabellini
2017-05-25 10:17 ` Julien Grall
2017-05-25 18:41   ` Stefano Stabellini
2016-05-13 15:14 Tamas K Lengyel
2015-10-01 16:59 Tamas K Lengyel
2015-10-01 17:04 ` Wei Liu
2014-10-30 10:54 Jan Vejvalka
2014-10-30 14:39 ` Ian Campbell
2014-10-31  6:35   ` Jan Vejvalka
2014-10-30 14:58 ` Roger Pau Monné
2014-01-20 22:49 Don Slutz
2014-01-20 23:35 ` Konrad Rzeszutek Wilk
2014-01-23 10:51   ` Ian Campbell
2014-01-23 22:03   ` Don Slutz
2014-01-24 14:58     ` Konrad Rzeszutek Wilk
2014-01-24 16:43       ` Don Slutz
2014-01-24 19:06         ` Don Slutz
2014-01-24 19:20           ` Konrad Rzeszutek Wilk
2014-01-27  1:15           ` herbert cland
2012-09-19  7:04 Dariusz Krempa

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.