Not knowing the specifics behind which pieces of hardware you are considering, I would start by looking at the XZD manual in chapter 6, possibly section 6.4, and chapter 9. Communication between domains is typically done over a virtual network, xenbus/xenstore, libvchan, or a custom mechanism built on top of shared memory and/or event channels. See section 6.4 in our UM for an example using libvchan. http://dornerworks.com/wp-content/upload...Manual.pdf

I have a question related to this topic as well.
Does DomU have the access to the FPGA part by default, for example using AXI to send some data in Zynq MPSoC board?
If not, can I configure it in real-time? Or must I configure it when I create the kernel of DomU?

(08-14-2017, 01:21 PM)Nathan.Studer Wrote: DomU does not have access to the PL by default. To give DomU access to a PL device, the PL device and any supporting components must be passed through to the DomU.

If you need to share the device with other virtual machines then a paravirtual driver would be necessary.

Nate

Hello Nate,

Thank you for your guidance. I would like to follow up this topic.
So I followed the manual and successfully performed a para virtualization for ethernet.
I ran a Dom0 and a DomU, both were petalinux, and they shared an Ethernet connection via xenbridge (xenbr0). Would you give me some direction on how I can do the same for an IP in PL?
Thank you so much.

(12-06-2017, 10:24 PM)ariefgrand Wrote: I ran a Dom0 and a DomU, both were petalinux, and they shared an Ethernet connection via xenbridge (xenbr0). Would you give me some direction on how I can do the same for an IP in PL?

Ethernet IP?

Here are some general steps:

Create and Export PL Design. (If the IP uses DMA use a wrapper to hardwire AxProt of the DMA interface to 0b010.)