Re: Xen PV: Sample new PV driver for buffer sharing between domains

[Omkar Bolla <omkar.bolla@pathpartnertech.com>]

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

Hi,
>
> > I am trying to pass-through the display to guest domain. to do through
> > driver needs clocks. I have written simple basic clock pv frontend and
> > backend.
> > So I thought these clocks must be initialised before display driver
> > initialisation.
>
> The graphic driver should request the clock, right? So Linux will make
> sure to have the clock before initializing the display.
>

We are not using graphics(GPU), I think drm takes care of graphics. And all
clocks needed for display I enabled using clocks PV. Clocks i have checked
in host domain all got enabled properly.


> >
> > But if I start both domain and clocks script one after another, clock
> > got initialised properly. Problem solved.
> > But still i have some doubt, is it possible to do some thing in xenbits
> > src to start automatically when we start underprivileged domain?
>
> I am not entirely sure if we have a way to run a script during domain
> creation. Wei, do you know if that's possible?
>
> A workaround would be to create the domain paused, call the script and
> then unpause it.
>
> 42sh> xl create -p ...
> 42sh> ./myscript.sh
> 42sh> xl unpause <myguest>
>

Now, I am doing same way pause and unpauase domain to start PV and it is
working.

>
> >
> > I have one more question about pass-through
> > To implement pass through I took reference from below link
> > https://wiki.xen.org/images/1/17/Device_passthrough_xen.pdf
> >
> > I added 'xen-passthrough' to actual dom0 dtb and created new dtb with
> > below nodes in passthrough node
> >
> ============================================================================
> > dpe: dpe@10004000 {
> > compatible = "hisilicon,hi3660-dpe";
> > status = "ok";
> > #if 0
> > //ACTUAL REG PROPERTY of DISPLAY
> >                          reg = <0x0 0xE8600000 0x0 0x80000>,
> >                                          <0x0 0xFFF35000 0 0x1000>,
> >                                          <0x0 0xFFF0A000 0 0x1000>,
> >                                          <0x0 0xFFF31000 0 0x1000>,
> >                                          <0x0 0xE86C0000 0 0x10000>;
> > #endif
> > //reg = <0x0 0x10004000 0x0 0x80000>,
> > reg = <0x0 0x10004000 0x0 0x80000>,
> >        <0x0 0x10084000 0 0x1000>,
> >        <0x0 0x10085000 0 0x1000>,
> >        <0x0 0x10086000 0 0x1000>,
> >        <0x0 0x100C4000 0 0x10000>;
> > //      <0x0 0x10087000 0 0x10000>;
> >
> > interrupts = <0 245 4>;
> >
> > clocks = <&clk_xen HI3660_ACLK_GATE_DSS>,
> > <&clk_xen HI3660_PCLK_GATE_DSS>,
> > <&clk_xen HI3660_CLK_GATE_EDC0>,
> > <&clk_xen HI3660_CLK_GATE_LDI0>,
> > <&clk_xen HI3660_CLK_GATE_LDI1>,
> > <&clk_xen HI3660_CLK_GATE_DSS_AXI_MM>,
> > <&clk_xen HI3660_PCLK_GATE_MMBUF>;
> > clock-names = "aclk_dss",
> > "pclk_dss",
> > "clk_edc0",
> > "clk_ldi0",
> > "clk_ldi1",
> > "clk_dss_axi_mm",
> > "pclk_mmbuf";
> >
> > dma-coherent;
> >
> > port {
> > dpe_out: endpoint {
> > remote-endpoint = <&dsi_in>;
> > };
> > };
> > };
> >
> > dsi: dsi@10097000 {
> > compatible = "hisilicon,hi3660-dsi";
> > status = "ok";
> > #if 0
> > //ACTUAL REG PROPERTY of DISPLAY
> > reg = <0 0xE8601000 0 0x7F000>,
> >                                          <0 0xFFF35000 0 0x1000>;
> > #endif
> > //reg = <0 0x10097000 0 0x7F000>,
> > //<0 0x10116000 0 0x1000>;
> > reg = <0 0x10004000 0 0x80000>,
> > <0 0x10084000 0 0x1000>;
> >
> > clocks = <&clk_xen HI3660_CLK_GATE_TXDPHY0_REF>,
> > <&clk_xen HI3660_CLK_GATE_TXDPHY1_REF>,
> > <&clk_xen HI3660_CLK_GATE_TXDPHY0_CFG>,
> > <&clk_xen HI3660_CLK_GATE_TXDPHY1_CFG>,
> > <&clk_xen HI3660_PCLK_GATE_DSI0>,
> > <&clk_xen HI3660_PCLK_GATE_DSI1>;
> > clock-names = "clk_txdphy0_ref",
> > "clk_txdphy1_ref",
> > "clk_txdphy0_cfg",
> > "clk_txdphy1_cfg",
> > "pclk_dsi0",
> > "pclk_dsi1";
> >
> > #address-cells = <1>;
> > #size-cells = <0>;
> >
> > };
> > #endif
> > clocks {
> > compatible = "simple-bus";
> > #address-cells = <2>;
> > #size-cells = <2>;
> > ranges;
> > clk_xen: xen_clk@0 {
> > compatible = "xen,xen-vclk";
> > #clock-cells = <1>;
> > };
> > };
> >
> ============================================================================
> > Below is my 'debian.cfg' file:
> >
> ============================================================================
> > kernel = "/debian/Image"
> > device_tree="/debian/domu.dtb"
> > memory = 512
> > vcpus = 8
> > cpus = "all"
> > name="debian"
> >
> > ################# DPE ################
> > #iomem = [ "0xE8600,0x80@0x10004", "0xFFF35,1@0x10084",
> > "0xFFF0A,1@0x10085", "0xFFF31,1@0x10086", "0xE86C0,10@0x10087"]
> > #iomem = [ "0xE8600,0x80", "0xFFF35,1", "0xFFF0A,1", "0xFFF31,1",
> > "0xE86C0,10"]
> > irqs = [ 277 ]
> >
> > iomem = [ "0xE8600,80@0x10004" ]
> >
> > iomem = [ "0xFFF35,1@0x10084" ]
> > iomem = [ "0xFFF0A,1@0x10085" ]
> > iomem = [ "0xFFF31,1@0x10086" ]
> > iomem = [ "0xE86C0,10@0x100C4"]
> > #iomem = [ "0xE86C0,10@0x10087"]
> > #iomem = [ "0xE8600,80@0x00000" ]
> >
> > ################# DPE ################
> > ################# DSI ################
> > #iomem = [ "0xE8601,0x7F", "0xFFF35,1"]
> > #iomem = [ "0xE8601,0x7F@0x10097", "0xFFF35,1@0x10116",
> > "0xE8601,0x7F@0x10195"]
> >
> > #iomem = [ "0xE8601,7F@0x10097" ]
> > #iomem = [ "0xFFF35,1@0x10116" ]
> >
> >
> > iomem = [ "0xE8601,7F@0x10005" ]
> > iomem = [ "0xFFF35,1@0x10084" ]
> > ################# DSI ################
> >
> > #vif = ['mac=00:16:3e:64:b8:40,bridge=xenbr0']
> > #nics = 1
> > #vif = [ 'eth0=00:60:00:00:00:01' ]
> >
> > disk = ['/dev/loop1,raw,xvda,w']
> > extra = "earlyprintk=xenboot console=hvc0 root=/dev/xvda rootfstype=ext4
> > rw video=HDMI-A-1:1280x720@60"
> >
> ============================================================================
> > Here I am using same io space(GFNs) for DPE and DSI nodes, and having
> > same below error
> > and tried with different GFNs and giving same error.
> >
> > But adding this, Every thing is good but when i am trying to remap iomem
> > second time, having below error
>
> Who is going the remap? The guest? Also, can you expand what you mean by
> it crash the second time. Is it during the remap, or access the new
> mapped region?
>
Here, Guest(domain-U) is remapping in display driver.
In display driver remapping is successful and yesterday i found when i try
to access
remapped region domain-U giving that crash, "Unhandled fault: ttbr address
size fault"

>


> >
> ============================================================================
> > [    3.215021] OF: rrrrrrrrrrrr: start: 0x10004000, sz = 0x80000
> > [    3.215062] [DISPLAY] dsi_parse_dt(): 1536: of device:
> > /passthrough/dsi@10097000
> > [    3.215083] [DISPLAY] dsi_parse_dt(): 1537:
> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > [    3.215108] [DISPLAY] dsi_parse_dt(): 1540: ctx->base:
> ffffff800bd01000
> > [    3.215126] [DISPLAY] dsi_parse_dt(): 1541:
> > [    3.215136] OF: rrrrrrrrrrrr: start: 0x10084000, sz = 0x1000
> > [    3.215169] [DISPLAY] dsi_parse_dt(): 1548:
> > [    4.159087] [DISPLAY] dsi_parse_dt(): 1563:
> > [    4.159092] [DISPLAY] dsi_parse_dt(): 1568:
> > [    4.159132] [D][XEN_VCLK]xen_vclk_xfer(): 163: buffer:
> clk_txdphy0_ref,1
> > [    4.159163] [D][XEN_VCLK]xen_vclk_xfer(): 164:
> > *******************************************
> > [    4.159399] [D][XEN_VCLK]xen_vclk_xfer(): 170:
> > *******************************************
> > [    4.159626] [D][XEN_VCLK]xen_vclk_xfer(): 176: Sending IRQ_DATA to
> > domain-0
> > [    4.160218] [D][XEN_VCLK]xen_vclk_interrupt(): 446: IRQ(13) from
> > domain 0 fired!!!
> > [    4.160359] [D][XEN_VCLK]vclk_fe_bh(): 394: irq_status: 0x3
> > [    4.160532] [D][XEN_VCLK]vclk_fe_bh(): 407: ACK Recieved from dom-0
> > [    4.160542] [D][XEN_VCLK]xen_vclk_xfer(): 179: Xfer Done
> > [    4.160545] [D][XEN_VCLK]xen_of_clk_src_onecell_get(): 286:  Xfer
> done...
> > [    4.160554] [DISPLAY] dsi_parse_dt(): 1575:
> > [    4.160560] [D][XEN_VCLK]vclk_round_rate(): 224:  called...
> > [    4.160567] [D][XEN_VCLK]xen_vclk_xfer(): 163: buffer:
> > clk_txdphy0_ref,4,19200000
> > [    4.160570] [D][XEN_VCLK]xen_vclk_xfer(): 164:
> > *******************************************
> > [    4.161095] [D][XEN_VCLK]xen_vclk_xfer(): 170:
> > *******************************************
> > [    4.161331] [D][XEN_VCLK]xen_vclk_xfer(): 176: Sending IRQ_DATA to
> > domain-0
> > [    4.161946] [D][XEN_VCLK]xen_vclk_interrupt(): 446: IRQ(13) from
> > domain 0 fired!!!
> > [    4.162120] [D][XEN_VCLK]vclk_fe_bh(): 394: irq_status: 0x3
> > [    4.162284] [D][XEN_VCLK]vclk_fe_bh(): 407: ACK Recieved from dom-0
> > [    4.162295] [D][XEN_VCLK]xen_vclk_xfer(): 179: Xfer Done
> > [    4.162301] [DISPLAY] dsi_parse_dt(): 1583:
> > [    4.162314] [D][XEN_VCLK]xen_vclk_xfer(): 163: buffer:
> clk_txdphy0_cfg,1
> > [    4.162316] [D][XEN_VCLK]xen_vclk_xfer(): 164:
> > *******************************************
> > [    4.162641] [D][XEN_VCLK]xen_vclk_xfer(): 170:
> > *******************************************
> > [    4.162984] [D][XEN_VCLK]xen_vclk_xfer(): 176: Sending IRQ_DATA to
> > domain-0
> > [    4.163596] [D][XEN_VCLK]xen_vclk_interrupt(): 446: IRQ(13) from
> > domain 0 fired!!!
> > [    4.167753] [D][XEN_VCLK]vclk_fe_bh(): 394: irq_status: 0x3
> > [    4.167955] [D][XEN_VCLK]vclk_fe_bh(): 407: ACK Recieved from dom-0
> > [    4.167968] [D][XEN_VCLK]xen_vclk_xfer(): 179: Xfer Done
> > [    4.167971] [D][XEN_VCLK]xen_of_clk_src_onecell_get(): 286:  Xfer
> done...
> > [    4.167979] [DISPLAY] dsi_parse_dt(): 1593:
> > [    4.167982] [D][XEN_VCLK]vclk_round_rate(): 224:  called...
> > [    4.167985] [D][XEN_VCLK]xen_vclk_xfer(): 163: buffer:
> > clk_txdphy0_cfg,4,19200000
> > [    4.167992] [D][XEN_VCLK]xen_vclk_xfer(): 164:
> > *******************************************
> > [    4.168244] [D][XEN_VCLK]xen_vclk_xfer(): 170:
> > *******************************************
> > [    4.168476] [D][XEN_VCLK]xen_vclk_xfer(): 176: Sending IRQ_DATA to
> > domain-0
> > [    4.169101] [D][XEN_VCLK]xen_vclk_interrupt(): 446: IRQ(13) from
> > domain 0 fired!!!
> > [    4.169262] [D][XEN_VCLK]vclk_fe_bh(): 394: irq_status: 0x3
> > [    4.169448] [D][XEN_VCLK]vclk_fe_bh(): 407: ACK Recieved from dom-0
> > [    4.169491] [D][XEN_VCLK]xen_vclk_xfer(): 179: Xfer Done
> > [    4.169510] [DISPLAY] dsi_parse_dt(): 1601:
> > [    4.169535] [D][XEN_VCLK]xen_vclk_xfer(): 163: buffer: pclk_dsi0,1
> > [    4.169554] [D][XEN_VCLK]xen_vclk_xfer(): 164:
> > *******************************************
> > [    4.169803] [D][XEN_VCLK]xen_vclk_xfer(): 170:
> > *******************************************
> > [    4.170019] [D][XEN_VCLK]xen_vclk_xfer(): 176: Sending IRQ_DATA to
> > domain-0
> > [    4.170619] [D][XEN_VCLK]xen_vclk_interrupt(): 446: IRQ(13) from
> > domain 0 fired!!!
> > [    4.170779] [D][XEN_VCLK]vclk_fe_bh(): 394: irq_status: 0x3
> > [    4.170965] [D][XEN_VCLK]vclk_fe_bh(): 407: ACK Recieved from dom-0
> > [    4.170978] [D][XEN_VCLK]xen_vclk_xfer(): 179: Xfer Done
> > [    4.170981] [D][XEN_VCLK]xen_of_clk_src_onecell_get(): 286:  Xfer
> done...
> > [    4.170989] [DISPLAY] dsi_parse_dt(): 1611:
> > [    4.170992] [DISPLAY] dsi_probe(): 1654: Before component add
> > [    4.170997] [DISPLAY] compare_of(): 242:
> > [    4.171002] [DISPLAY] kirin_drm_bind(): 257:
> > [    4.171004] [drm] +.
> > [    4.171386] [DISPLAY] kirin_drm_kms_init(): 105:
> > [    4.171391] [drm] +.
> > [    4.212543] [DISPLAY] kirin_drm_mode_config_init(): 91:
> > [    4.212547] [DISPLAY] dss_drm_init(): 638:
> > [    4.212563] [drm] +.
> > [    4.212585] [DISPLAY] dss_dts_parse(): 513:
> > [    4.212603] [DISPLAY] dss_dts_parse(): 530: of device:
> > /passthrough/dpe@10004000
> > [    4.212635] [DISPLAY] dss_dts_parse(): 531:
> >
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > [    4.212661] [DISPLAY] dss_dts_parse(): 532: ctx->base:
> ffffff800bd00000
> > [    4.212688] Unhandled fault: ttbr address size fault (0x96000000) at
> > 0xffffff800bd01000
>
> IIRC, this error usually happen when the region is not mapped in
> stage-2. On Xen debug-build (CONFIG_DEBUG=y in .config) you should get
> some log if there was a data abort in stage-2.
>
> I enabled (CONFIG_DEBUG=y in .config) in xenbits src,  I dont have any
log from xen.
also checked 'xl dmesg'  but no log from xen.

How to find GFNs from xen? I mean, xen maps region from RAM memory of
domain-u or
maps to memory of Domain-0 and give access to domain-u?

I am sharing log of xl dmesg after enabling guest log level:
======================================
root@hikey960:/debian# xl dmesg
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000000000000 - 000000001abfffff
(XEN) RAM: 000000001ad88000 - 0000000031ffffff
(XEN) RAM: 0000000032101000 - 000000003dffffff
(XEN) RAM: 0000000040000000 - 000000004aee9fff
(XEN) RAM: 0000000089cc0000 - 00000000b8427fff
(XEN) RAM: 00000000b9af0000 - 00000000b9baffff
(XEN) RAM: 00000000b9c50000 - 00000000b9c54fff
(XEN) RAM: 00000000b9c56000 - 00000000b9d4ffff
(XEN) RAM: 00000000ba114000 - 00000000ba11bfff
(XEN) RAM: 00000000ba11c000 - 00000000bdbf1fff
(XEN) RAM: 00000000bdbf2000 - 00000000bdca2fff
(XEN) RAM: 00000000bdca3000 - 00000000bdd58fff
(XEN) RAM: 00000000bdd59000 - 00000000bef4ffff
(XEN) RAM: 00000000bef50000 - 00000000bef54fff
(XEN) RAM: 00000000bef55000 - 00000000bf0dffff
(XEN) RAM: 00000000bf0e0000 - 00000000bf12ffff
(XEN) RAM: 00000000bf180000 - 00000000bf188fff
(XEN) RAM: 00000000bf189000 - 00000000bfffffff
(XEN) RAM: 00000000c0000000 - 00000000dfffffff
(XEN) RAM: 0000000200000000 - 000000021fffffff
(XEN)
(XEN) MODULE[0]: 00000000b8428000 - 00000000b8436000 Device Tree
(XEN) MODULE[1]: 00000000b8544000 - 00000000b997ca00 Kernel
 console=tty0 console=hvc0 root=/dev/sdd14 rootwait rw rootfstype=ext4
efi=noruntime video=HDMI-A
-1:1280x720@60
(XEN)
(XEN) Command line: loglvl=all console=dtuart dtuart=/soc/serial@fff32000
dom0_mem=512M efi=no-rs guest_loglvl=all
(XEN) Placing Xen at 0x000000001aa00000-0x000000001ac00000
(XEN) Update BOOTMOD_XEN from 00000000b8436000-00000000b8536d81 =>
000000001aa00000-000000001ab00d81
(XEN) Domain heap initialised
(XEN) Platform: Generic System
(XEN) Looking for dtuart at "/soc/serial@fff32000", options ""
 Xen 4.8.5-pre
(XEN) Xen version 4.8.5-pre (omkar.bolla@) (aarch64-linux-gnu-gcc (Linaro
GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Fri Nov  2 10:40:45 IST 2018
(XEN) Latest ChangeSet:
(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.1 for SMP bringup
(XEN) SMP: Allowing 8 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000e82b1000
(XEN)         gic_cpu_addr=00000000e82b2000
(XEN)         gic_hyp_addr=00000000e82b4000
(XEN)         gic_vcpu_addr=00000000e82b6000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
(XEN) CPU 3 booted.
(XEN) Bringing up CPU4
(XEN) CPU 4 booted.
(XEN) Bringing up CPU5
(XEN) CPU 5 booted.
(XEN) Bringing up CPU6
(XEN) CPU 6 booted.
(XEN) Bringing up CPU7
(XEN) CPU 7 booted.
(XEN) Brought up 8 CPUs
(XEN) P2M: 40-bit IPA with 40-bit PA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) I/O virtualisation disabled
(XEN) build-id: baea0accc1a90dbddfdab8bcec069906a9b45ba6
(XEN) alternatives: Patching with alt table 00000000400a4868 ->
00000000400a4c04
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 00000000b8544000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x000000c0000000-0x000000e0000000 (512MB)
(XEN) Grant table range: 0x0000001aa00000-0x0000001aa5f000
(XEN) /framebuffer@E8600000 passthrough = 0 nirq = 5 naddr = 7
(XEN)   - MMIO: 00e8600000 - 00e8680000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN)   - MMIO: 00fff35000 - 00fff36000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN)   - MMIO: 00fff0a000 - 00fff0b000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN)   - MMIO: 00e8a09000 - 00e8a0a000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN)   - MMIO: 00e86c0000 - 00e86d0000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN)   - MMIO: 00fff02000 - 00fff03000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN)   - MMIO: 00fff31000 - 00fff32000 P2MType=5
(XEN) Device Node: /framebuffer@E8600000
(XEN) /mali@E82C0000 passthrough = 0 nirq = 3 naddr = 1
(XEN)   - MMIO: 00e82c0000 - 00e82c4000 P2MType=5
(XEN) Device Node: /mali@E82C0000
(XEN) /dpe@E8600000 passthrough = 0 nirq = 1 naddr = 5
(XEN)   - MMIO: 00e8600000 - 00e8680000 P2MType=5
(XEN) Device Node: /dpe@E8600000
(XEN)   - MMIO: 00fff35000 - 00fff36000 P2MType=5
(XEN) Device Node: /dpe@E8600000
(XEN)   - MMIO: 00fff0a000 - 00fff0b000 P2MType=5
(XEN) Device Node: /dpe@E8600000
(XEN)   - MMIO: 00fff31000 - 00fff32000 P2MType=5
(XEN) Device Node: /dpe@E8600000
(XEN)   - MMIO: 00e86c0000 - 00e86d0000 P2MType=5
(XEN) Device Node: /dpe@E8600000
(XEN) /dsi@E8601000 passthrough = 0 nirq = 0 naddr = 2
(XEN)   - MMIO: 00e8601000 - 00e8680000 P2MType=5
(XEN) Device Node: /dsi@E8601000
(XEN)   - MMIO: 00fff35000 - 00fff36000 P2MType=5
(XEN) Device Node: /dsi@E8601000
(XEN) Loading zImage from 00000000b8544000 to
00000000c0080000-00000000c14b8a00
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x00000000c8000000-0x00000000c800a8a1
(XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
(XEN) .........done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
to Xen)
(XEN) Freed 272kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER32
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER36
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER40
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER44
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v4: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v5: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v6: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v7: vGICD: unhandled word write 0xffffffff to ICACTIVER0
-------------------------------------------------------------------------------
(XEN) memory_map:add: dom1 gfn=10084 mfn=fff35 nr=1
-------------------------------------------------------------------------------
(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
(XEN) d1v4: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d1v5: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d1v6: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d1v7: vGICD: unhandled word write 0xffffffff to ICACTIVER0
======================================
After enabling guest log level, It is showing only one io region mapped
instead of all. Why?



> Cheers,
>
> --
> Julien Grall
>

Thanks,
Omkar B

-- 






This
message contains confidential information and is intended only 
for the
individual(s) named. If you are not the intended
recipient, you are 
notified that disclosing, copying, distributing or taking any
action in 
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail 
from your system. E-mail transmission
cannot be guaranteed to be secured or 
error-free as information could be
intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain
viruses. The sender therefore does 
not accept liability for any errors or
omissions in the contents of this 
message, which arise as a result of e-mail
transmission.

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

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

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