From: Wei Liu <wei.liu2@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Peng Fan <van.freenix@gmail.com>, Peng Fan <peng.fan@nxp.com>,
sstabellini@kernel.org, Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH V4] xen/arm: domain_build: allocate lowmem for dom0 as much as possible
Date: Fri, 11 Nov 2016 01:41:31 +0000 [thread overview]
Message-ID: <20161111014131.GH31926@citrix.com> (raw)
In-Reply-To: <13b190df-ac45-9e09-7952-b8c86ecfe3fe@arm.com>
On Thu, Nov 10, 2016 at 01:01:38PM +0000, Julien Grall wrote:
> (CC Wei as release manager)
>
> On 10/11/16 08:30, Peng Fan wrote:
> >Hi Julien,
>
> Hi Peng,
>
> >On Tue, Nov 01, 2016 at 02:42:06PM +0000, Julien Grall wrote:
> >>Hi Peng,
> >>
> >>Sorry for the late answer.
> >>
> >>On 23/09/2016 03:55, Peng Fan wrote:
> >>>On AArch64 SoCs, some IPs may only have the capability to access
> >>>32 bits address space. The physical memory assigned for Dom0 maybe
> >>>not in 4GB address space, then the IPs will not work properly.
> >>>So need to allocate memory under 4GB for Dom0.
> >>>
> >>>There is no restriction that how much lowmem needs to be allocated for
> >>>Dom0 ,so allocate lowmem as much as possible for Dom0.
> >>>
> >>>This patch does not affect 32-bit domain, because Variable "lowmem" is
> >>>set to true at the beginning. If failed to allocate bank0 under 4GB,
> >>>need to panic for 32-bit domain, because 32-bit domain requires bank0
> >>>be allocated under 4GB.
> >>>
> >>>For 64-bit domain, set "lowmem" to false, and continue allocating
> >>>memory from above 4GB.
> >>>
> >>>Signed-off-by: Peng Fan <peng.fan@nxp.com>
> >>>Cc: Stefano Stabellini <sstabellini@kernel.org>
> >>>Cc: Julien Grall <julien.grall@arm.com>
> >>
> >>Reviewed-by: Julien Grall <julien.grall@arm.com>
> >>
> >>I am undecided whether this should be considered as a bug fix for Xen 4.8.
> >>Are you aware of any ARM64 platform we currently support requiring allocation
> >>of memory below 4GB?
> >
> >I have no idea about this (:, but I think this is a bug fix. Alought current
> >supported platforms works well, users may choose 4.8 to support their
> >new platform which has the limitation to access 64bit address.
>
> We are already late in the release process (rc5) for Xen 4.8. So we need to
> be careful when including a bug fix and evaluate the pros and cons.
>
> This patch is modifying the DOM0 memory layout for all 64-bit platforms. So
> it could potentially break one of the platform we officially support (see
> [1] for a non-exhaustive list). We don't have a test suite running
> automatically for ARM64 at the moment (it is been working on), this means
> that manual testing needs to be done. I am not aware of any platform, in the
> list we supports, having this issue so I prefer to stay on the safe side and
> defer this patch for Xen 4.9.
>
> If a user cares about Xen 4.8 for their platforms, then they could request
> the patch to be backported in Xen 4.8 after the release and after extensive
> testing in staging.
>
I agree with your reasoning.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-11 1:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 2:55 [PATCH V4] xen/arm: domain_build: allocate lowmem for dom0 as much as possible Peng Fan
2016-10-08 2:25 ` Peng Fan
2016-11-01 14:42 ` Julien Grall
2016-11-01 18:12 ` Stefano Stabellini
2016-11-10 8:30 ` Peng Fan
2016-11-10 13:01 ` Julien Grall
2016-11-11 1:10 ` Peng Fan
2016-11-11 1:41 ` Wei Liu [this message]
2016-11-11 11:35 ` Andrii Anisov
2016-11-11 11:59 ` Julien Grall
2016-11-11 14:24 ` Andrii Anisov
2016-11-11 14:39 ` Andrii Anisov
2016-11-11 16:02 ` Julien Grall
2016-11-11 19:27 ` Stefano Stabellini
2016-11-14 8:54 ` Andrii Anisov
2016-11-14 9:11 ` Andrii Anisov
2016-11-14 20:30 ` Julien Grall
2016-11-16 14:49 ` Andrii Anisov
2016-11-14 9:25 ` Andrii Anisov
2016-11-14 9:43 ` Andrii Anisov
2016-11-14 23:28 ` Stefano Stabellini
2016-11-16 15:28 ` Andrii Anisov
2016-11-17 17:21 ` Stefano Stabellini
2016-11-18 18:00 ` Stefano Stabellini
2016-11-21 11:04 ` Andrii Anisov
2016-11-21 17:52 ` Stefano Stabellini
2016-11-11 19:25 ` Stefano Stabellini
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=20161111014131.GH31926@citrix.com \
--to=wei.liu2@citrix.com \
--cc=julien.grall@arm.com \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=van.freenix@gmail.com \
--cc=xen-devel@lists.xen.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).