|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen PV: Sample new PV driver for buffer sharing between domains
(+ Wei) On 11/1/18 9:15 AM, Omkar Bolla wrote: Hi,May I ask why you need the dependency on the rootfs?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. 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> 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.pdfI added 'xen-passthrough' to actual dom0 dtb and created new dtb with below nodes in passthrough node 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? ============================================================================ [ 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. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |