From: Peng Fan <van.freenix@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>
Subject: Re: [ARM] Handling CMA pool device nodes in Dom0
Date: Fri, 2 Dec 2016 15:26:02 +0800 [thread overview]
Message-ID: <20161202072559.GA8090@linux-7smt.suse> (raw)
In-Reply-To: <f8f67a66-af2b-064f-5699-340bbe7d4308@arm.com>
On Tue, Nov 29, 2016 at 01:49:51PM +0000, Julien Grall wrote:
>(CC Stefano)
>
>On 25/11/16 12:19, Iurii Mykhalskyi wrote:
>>Hello!
>
>Hi Iurii,
>
>>
>>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?
How about using "alloc-ranges"?
Regards,
Peng.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-02 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 12:19 [ARM] Handling CMA pool device nodes in Dom0 Iurii Mykhalskyi
2016-11-29 13:49 ` 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 ` Peng Fan [this message]
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=20161202072559.GA8090@linux-7smt.suse \
--to=van.freenix@gmail.com \
--cc=iurii.mykhalskyi@globallogic.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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).