xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>
To: xen-devel@lists.xenproject.org
Cc: Julien Grall <julien.grall@arm.com>
Subject: [ARM] Handling CMA pool device nodes in Dom0
Date: Fri, 25 Nov 2016 14:19:57 +0200	[thread overview]
Message-ID: <CAC+yBMtsFSHe32_=EST+bgK0p9HTLnLEt5fUmb+7Bah=s1nyGA@mail.gmail.com> (raw)


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

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 = "shared-dma-pool";
reusable;
reg = <0x00000000 0x57000000 0x0 0x01000000>;
};

2:
linux,cma {
compatible = "shared-dma-pool";
reusable;
reg = <0x00000000 0x58000000 0x0 0x18000000>;
linux,cma-default;
};

During Dom0 allocation, we can't guarantee, that allocated memory will
contain mentioned regions.
In second сase, we can actually hardcode mapped region by using separate
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.

-- 

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/>
http://www.globallogic.com/email_disclaimer.txt

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

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

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

             reply	other threads:[~2016-11-25 12:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 12:19 Iurii Mykhalskyi [this message]
2016-11-29 13:49 ` [ARM] Handling CMA pool device nodes in Dom0 Julien Grall
2016-12-01  0:12   ` Stefano Stabellini
2017-07-26 15:04     ` Reserved-memory node handling in XEN ( WAS Re: [ARM] Handling CMA pool device nodes in Dom0) Andrii Anisov
2017-07-26 17:06       ` Julien Grall
2017-07-27  9:24         ` Andrii Anisov
2017-07-27  9:55           ` Julien Grall
2017-07-27 10:36             ` Andrii Anisov
2017-07-27 10:56               ` Julien Grall
2017-07-27 11:02                 ` Andrii Anisov
2016-12-02  7:26   ` [ARM] Handling CMA pool device nodes in Dom0 Peng Fan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC+yBMtsFSHe32_=EST+bgK0p9HTLnLEt5fUmb+7Bah=s1nyGA@mail.gmail.com' \
    --to=iurii.mykhalskyi@globallogic.com \
    --cc=julien.grall@arm.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).