From mboxrd@z Thu Jan 1 00:00:00 1970 From: Iurii Mykhalskyi Subject: [ARM] Handling CMA pool device nodes in Dom0 Date: Fri, 25 Nov 2016 14:19:57 +0200 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0840193763297704408==" Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cAFUX-0007gq-2c for xen-devel@lists.xenproject.org; Fri, 25 Nov 2016 12:20:33 +0000 Received: by mail-wj0-f181.google.com with SMTP id mp19so57659097wjc.1 for ; Fri, 25 Nov 2016 04:20:28 -0800 (PST) List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xenproject.org Cc: Julien Grall List-Id: xen-devel@lists.xenproject.org --===============0840193763297704408== Content-Type: multipart/alternative; boundary=047d7b5da8b5b676d105421f2576 --047d7b5da8b5b676d105421f2576 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello! I'm working under Renesas Gen3 H3 board with 4GB RAM (Salvator-X) support in Xen mainline. Salvator-X has several CMA pool nodes, for example: 1: adsp_reserved: linux,adsp { compatible =3D "shared-dma-pool"; reusable; reg =3D <0x00000000 0x57000000 0x0 0x01000000>; }; 2: linux,cma { compatible =3D "shared-dma-pool"; reusable; reg =3D <0x00000000 0x58000000 0x0 0x18000000>; linux,cma-default; }; During Dom0 allocation, we can't guarantee, that allocated memory will contain mentioned regions. In second =D1=81ase, we can actually hardcode mapped region by using separa= te DTS for Dom0 with changed memory regions. But for first one, this in not an option - this pool is used for audio DSP and its firmware relies on this addresses. What is the correct way to solve this situation? Does Xen has some mechanism to handle such cases? Thank you. --=20 Iurii Mykhalskyi | Senior Software Engineer GlobalLogic P +38.044.492.9695x3664 M +38.096.311.5467 S mad-nemoi www.globallogic.com http://www.globallogic.com/email_disclaimer.txt --047d7b5da8b5b676d105421f2576 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello!

I'm working under Renesas Ge= n3 H3 board with 4GB RAM (Salvator-X) support in Xen mainline.
Salvator-X has several =C2=A0CMA pool nodes, for example:

1:
<= div>adsp_reserved: linux,adsp {
= compatible =3D "shared-dma-pool";
reusable;
re= g =3D <0x00000000 0x57000000 0x0 0x01000000>;
};
=
2:
linux,cma {
compatible =3D "shared-d= ma-pool";
reusable;
reg =3D <0x00000000 0x58000000 0x0 = 0x18000000>;
linux,cma-default;
};

<= /div>
During Dom0 allocation, we can't guarantee, that allocated me= mory will contain mentioned regions.
In second =D1=81ase, we can = actually hardcode mapped region by using separate DTS for Dom0 with changed= memory regions.=C2=A0
But for first one, this in not an option -= this pool is used for audio DSP and its firmware relies on this addresses.= =C2=A0

What is the correct way to solve this situa= tion?
Does Xen has some mechanism to handle such cases?

Thank you.

--

Iurii Mykhalskyi | Senior Software Engineer
GlobalLogic
P= =C2=A0+38.044.492.9695x3664=C2=A0 M +38.096.311.5467= =C2=A0 S mad-nemoi
www.globallogic.com

http://www.globallogic.com/email_disclaimer.txt=
--047d7b5da8b5b676d105421f2576-- --===============0840193763297704408== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============0840193763297704408==--