Re: [Xen-devel] [XEN][ARM64] PV DRM failing to convert virtual to physical address
Sorry for top-posting. Well, from the logs I see that those failures come before PV DRM even creates any shared buffers which could be the problem: when you see (XEN) p2m.c:1456: d2v1: gvirt_to_maddr failed va=0x80001df5205f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80001df8005f flags=0x1 par=0x809 in your logs this at the time when PV DRM had read the configuration and created shared rings, but it hasn't yet allocated any buffers so far which might be the source of p2m complaints. So, unfortunately, I think you would need to debug more to understand from where those come. And, please rebuild the PV DRM as a module and collect DRM logs in DomU. On 12/19/18 7:45 AM, Vikram K wrote: Hello Oleksandr, Please find the attached log file. Could please provide some pointers on how test DomU display. modetest, weston - whatever you have in your rootfs On Tue, Dec 18, 2018 at 12:06 PM Oleksandr Andrushchenko mailto:andr2...@gmail.com>> wrote: Hello, Vikram! > * We are using 64 bit arm platform. > * Linux 4.20 Kernel in DomU with PV DRM front-end drivers. > >> Do you have [1] enabled in your DomD kernel? Earlier this configuration was not enabled. Enabled it now. Well, this just adds zero-copying, but shouldn't change the behavior so much > > * Xen-4.12 unstable version. > >> We never tested PV DRM with 4.12 so far, did you try with 4.10 for example? Xen-4.8 is working on our platform. Xen-4.9 to Xen-4.11 version fails while initializing CPU on our platform. Recently we received patch from Julien for Xen-4.12 unstable version, which has fix. Tried to apply patch on Xen-4.10 stable facing build issue. This is where we are at the moment and have all PV drivers running smoothly > * Able to build displ_be application and also its dependencies. > > Added below configuration in Domain-U config file.*| > |* > *|vdispl = [ 'backend=Domain-0,be-alloc=0,connectors=HDMI-A-1:1920x1080']|* > >> Do you really have DomD as your configuration says? Sorry it not DomD it is Domain-0. >> Not Dom0 running the backend? Domain-0 is running in Dom0 and debian is running as DomU. > Before launching the DomU ran the displ_be application in the > background. > $ displ_be -m DRM -v *:Debug & Please add display back-end logs > > Started Domain-U. > $ xl create -c debian.cfg > >> Could you please build the PV DRM driver as module, >> Built as module. then run the following commands: echo 0xff > /sys/module/drm/parameters/debug echo 8 > /proc/sys/kernel/printk This needs to be done *before* you insmod the PV DRM driver >> and get back with DRM logs in DomU? Please find the attached log file -- Thanks & Regards Vikram KS 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. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [XEN][ARM64] PV DRM failing to convert virtual to physical address
Hello Oleksandr, Please find the attached log file. Could please provide some pointers on how test DomU display. On Tue, Dec 18, 2018 at 12:06 PM Oleksandr Andrushchenko wrote: Hello, Vikram! > * We are using 64 bit arm platform. > * Linux 4.20 Kernel in DomU with PV DRM front-end drivers. > >> Do you have [1] enabled in your DomD kernel? Earlier this configuration was not enabled. Enabled it now. > > * Xen-4.12 unstable version. > >> We never tested PV DRM with 4.12 so far, did you try with 4.10 for example? Xen-4.8 is working on our platform. Xen-4.9 to Xen-4.11 version fails while initializing CPU on our platform. Recently we received patch from Julien for Xen-4.12 unstable version, which has fix. Tried to apply patch on Xen-4.10 stable facing build issue. This is where we are at the moment and have all PV drivers running smoothly > * Able to build displ_be application and also its dependencies. > > Added below configuration in Domain-U config file.*| > |* > *|vdispl = [ 'backend=Domain-0,be-alloc=0,connectors=HDMI-A-1:1920x1080']|* > >> Do you really have DomD as your configuration says? Sorry it not DomD it is Domain-0. >> Not Dom0 running the backend? Domain-0 is running in Dom0 and debian is running as DomU. > Before launching the DomU ran the displ_be application in the > background. > $ displ_be -m DRM -v *:Debug & Please add display back-end logs > > Started Domain-U. > $ xl create -c debian.cfg > >> Could you please build the PV DRM driver as module, >> Built as module. then run the following commands: echo 0xff > /sys/module/drm/parameters/debug echo 8 > /proc/sys/kernel/printk >> and get back with DRM logs in DomU? Please find the attached log file -- Thanks & Regards Vikram KS -- 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. === $ displ_be -m DRM -v *:Debug & 19.12.18 05:13:11.447 | Main | INF - backend version: v0.2.1-5-g7fc0-dirty 19.12.18 05:13:11.454 | Main | INF - libxenbe version: v0.2.1-2-g6769-dirty 19.12.18 05:13:11.461 | Drm | DBG - Create Drm card: /dev/dri/card0, FD: 3 19.12.18 05:13:11.476 | Drm | DBG - Connector id: 30, name: HDMI-A-1, connected: 1 19.12.18 05:13:11.485 | XenStore | DBG - Create xen store 19.12.18 05:13:11.490 | XenStore | DBG - Read string domid : 0 19.12.18 05:13:11.496 | XenStore | DBG - Read int domid : 0 19.12.18 05:13:11.501 | DisplBackend | DBG - Create backend, device: vdispl, dom Id: 0 19.12.18 05:13:11.509 | Drm | DBG - Start 19.12.18 05:13:11.514 | XenStore | DBG - Start 19.12.18 05:13:11.518 | XenStore | DBG - Set watch: /local/domain/0/backend/vdispl 19.12.18 05:13:11.527 | XenStore | DBG - Watch triggered: /local/domain/0/backend/vdispl === $ create_domu_debian DomU boot logs: root@hikey960:~# create_domu_debian Parsing config from /debian/debian.cfg 19.12.18 05:21:42.465 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.474 | XenStore| DBG - Set watch: /local/domain/0/backend/vdispl/2 19.12.18 05:21:42.483 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.492 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.501 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.510 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.519 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.528 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl 19.12.18 05:21:42.536 | XenStore| DBG - Watch triggered: /local/domain/0/backend/vdispl/2 19.12.18 05:21:42.546 | DisplBackend| DBG - New frontend found, domid: 2, devid: 0 19.12.18 05:21:42.554 | XenStore| DBG - Create xen store 19.12.18 05:21:42.559 | DisplFrontend | DBG - Dom(2/0) Create frontend handler 19.12.18 05:21:42.567 | XenStore| DBG - Read string
Re: [Xen-devel] [XEN][ARM64] PV DRM failing to convert virtual to physical address
Hello, Vikram! First of all what makes you think this is related to PV DRM? Please see inline for more comments Thank you, Oleksandr On 12/18/18 7:26 AM, Vikram K wrote: Hello, When PV DRM is enabled and Domain-U is started xen is not able to converted virtual address to physical. Please provide input on resolving this issue. Please find the details below. * We are using 64 bit arm platform. * Linux 4.20 Kernel in DomU with PV DRM front-end drivers. Do you have [1] enabled in your DomD kernel? * Xen-4.12 unstable version. We never tested PV DRM with 4.12 so far, did you try with 4.10 for example? This is where we are at the moment and have all PV drivers running smoothly * Able to build displ_be application and also its dependencies. Added below configuration in Domain-U config file.*| |* *|vdispl = [ 'backend=DomD,be-alloc=0,connectors=HDMI-A-1:1920x1080']|* Do you really have DomD as your configuration says? Not Dom0 running the backend? Before launching the application ran the displ_be application in the background. $ displ_be -m DRM -v *:Debug Please add display backend logs Started Domain-U. $ xl create -c debian.cfg Could you please build the PV DRM driver as module, then run the following commands: echo 0xff > /sys/module/drm/parameters/debug echo 8 > /proc/sys/kernel/printk and get back with DRM logs in DomU? Getting below logs. Welcome to Debian GNU/Linux 9 (stretch)! (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 [ 2.601162] systemd[1]: Set hostname to . [ 2.613526] random: systemd: uninitialized urandom read (16 bytes re(XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 ad) (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 [snip] -- Thanks & Regards Vikram KS 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. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel [1] https://elixir.bootlin.com/linux/v4.20-rc7/source/drivers/xen/Kconfig#L175 ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] [XEN][ARM64] PV DRM failing to convert virtual to physical address
Hello, When PV DRM is enabled and Domain-U is started xen is not able to converted virtual address to physical. Please provide input on resolving this issue. Please find the details below. - We are using 64 bit arm platform. - Linux 4.20 Kernel in DomU with PV DRM front-end drivers. - Xen-4.12 unstable version. - Able to build displ_be application and also its dependencies. Added below configuration in Domain-U config file. *vdispl = [ 'backend=DomD,be-alloc=0,connectors=HDMI-A-1:1920x1080']* Before launching the application ran the displ_be application in the background. $ displ_be -m DRM -v *:Debug Started Domain-U. $ xl create -c debian.cfg Getting below logs. Welcome to Debian GNU/Linux 9 (stretch)! (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 [2.601162] systemd[1]: Set hostname to . [2.613526] random: systemd: uninitialized urandom read (16 bytes re(XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 ad) (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c050 flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v2: gvirt_to_maddr failed va=0x80003df6c05f flags=0x1 par=0x809 [3.006492] systemd[1]: Reached target Remote File Systems. [ OK ] Reached target Remote File Systems. [3.007179] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [3.007477] systemd[1]: Listening on Journal Socket. [ OK ] Listening on Journal Socket. [3.007742] systemd[1]: Listening on LVM2 metadata daemon socket. [ OK ] Listening on LVM2 metadata daemon socket. [3.007966] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ OK ] Listening on Device-mapper event daemon FIFOs. [3.008161] systemd[1]: Listening on Syslog Socket. [ OK ] Listening on Syslog Socket. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Created slice System Slice. Starting Remount Root and Kernel File Systems... Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling... [(XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df8305f flags=0x1 par=0x809 (XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df83050 flags=0x1 par=0x809 OK ] Created slice system-serial\x2dgetty.slice. Mounting Huge Pages File System... Starting Uncomplic(XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df8305f flags=0x1 par=0x809 ated firewall... [ OK ] Listening on LVM2 poll daemon socket. Starting Create Static Device Nodes in /d(XEN) p2m.c:1456: d2v3: gvirt_to_maddr failed va=0x80003df8305f flags=0x1 par=0x809 ev(XEN)
