From: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
To: Julien Grall <julien@xen.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
minyard@acm.org, Paul Durrant <paul@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <jgrall@amazon.com>,
roman@zededa.com, George Dunlap <george.dunlap@citrix.com>,
Jeff Kubascik <jeff.kubascik@dornerworks.com>,
Jan Beulich <jbeulich@suse.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH for-4.14 0/3] Remove the 1GB limitation on Rasberry Pi 4
Date: Tue, 19 May 2020 17:43:37 -0600 [thread overview]
Message-ID: <CABfawhkMEu0kMH7dac6OrUxpif8v+m7MeWePRg8UYL7MstJNFA@mail.gmail.com> (raw)
In-Reply-To: <297448b7-7837-cbe5-dee4-da80ca03cd29@xen.org>
On Tue, May 19, 2020 at 11:23 AM Julien Grall <julien@xen.org> wrote:
>
>
>
> On 19/05/2020 04:08, Tamas K Lengyel wrote:
> > On Mon, May 18, 2020 at 5:32 AM Julien Grall <julien@xen.org> wrote:
> >>
> >> From: Julien Grall <jgrall@amazon.com>
> >>
> >> Hi all,
> >>
> >> At the moment, a user who wants to boot Xen on the Raspberry Pi 4 can
> >> only use the first GB of memory.
> >>
> >> This is because several devices cannot DMA above 1GB but Xen doesn't
> >> necessarily allocate memory for Dom0 below 1GB.
> >>
> >> This small series is trying to address the problem by allowing a
> >> platform to restrict where Dom0 banks are allocated.
> >>
> >> This is also a candidate for Xen 4.14. Without it, a user will not be
> >> able to use all the RAM on the Raspberry Pi 4.
> >>
> >> This series has only be slighlty tested. I would appreciate more test on
> >> the Rasbperry Pi 4 to confirm this removing the restriction.
> >
> > Hi Julien,
>
> Hi,
>
> > could you post a git branch somewhere? I can try this on my rpi4 that
> > already runs 4.13.
>
> I have pushed a branch based on unstable and the v2 of the series:
>
> git://xenbits.xen.org/people/julieng/xen-unstable.git
>
> branch arm-dma/v2
>
I've updated my image I built with
https://github.com/tklengyel/xen-rpi4-builder a while ago and I've
defined 2048m as total_mem and Xen seems to be booting fine and passes
execution to dom0. With 512m being set as the Xen cmdline for dom0_mem
it was working. When I increased the mem for dom0 the boot is now
stuck at:
[ 1.427788] of_cfs_init
[ 1.429667] of_cfs_init: OK
[ 1.432561] clk: Not disabling unused clocks
[ 1.437239] Waiting for root device /dev/mmcblk0p2...
[ 1.451599] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.458156] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.464729] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.472804] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.479370] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.546902] random: fast init done
[ 1.564590] mmc1: new high speed SDIO card at address 0001
Could this be because the DTB I compiled from a fresh checkout of
https://github.com/raspberrypi/linux.git branch rpi-4.19.y whereas the
kernel itself is from a checkout ~5 months ago? I guess that must be
the cause because even if I decrease the dom0_mem to 512m it still
gets stuck at the same spot whereas it was booting fine before.
Tamas
next prev parent reply other threads:[~2020-05-19 23:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 11:30 [PATCH for-4.14 0/3] Remove the 1GB limitation on Rasberry Pi 4 Julien Grall
2020-05-18 11:30 ` [PATCH for-4.14 1/3] xen/arm: Allow a platform to override the DMA width Julien Grall
2020-05-18 18:24 ` Volodymyr Babchuk
2020-05-20 22:01 ` Stefano Stabellini
2020-05-18 11:30 ` [PATCH for-4.14 2/3] xen/arm: Take into account the DMA width when allocating Dom0 memory banks Julien Grall
2020-05-18 20:34 ` Volodymyr Babchuk
2020-05-19 16:55 ` Julien Grall
2020-05-18 11:30 ` [PATCH for-4.14 3/3] xen/arm: plat: Allocate as much as possible memory below 1GB for dom0 for RPI Julien Grall
2020-05-18 20:36 ` Volodymyr Babchuk
2020-05-19 0:02 ` Corey Minyard
2020-05-19 17:07 ` Julien Grall
2020-05-19 17:06 ` Julien Grall
2020-05-19 3:08 ` [PATCH for-4.14 0/3] Remove the 1GB limitation on Rasberry Pi 4 Tamas K Lengyel
2020-05-19 17:22 ` Julien Grall
2020-05-19 23:43 ` Tamas K Lengyel [this message]
2020-05-19 23:48 ` Stefano Stabellini
2020-05-19 23:50 ` Roman Shaposhnik
2020-05-20 2:15 ` Tamas K Lengyel
2020-05-20 2:28 ` Roman Shaposhnik
2020-05-20 3:06 ` Tamas K Lengyel
2020-05-20 22:13 ` Stefano Stabellini
2020-05-21 17:50 ` Julien Grall
2020-05-21 18:12 ` 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=CABfawhkMEu0kMH7dac6OrUxpif8v+m7MeWePRg8UYL7MstJNFA@mail.gmail.com \
--to=tamas.k.lengyel@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jeff.kubascik@dornerworks.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=minyard@acm.org \
--cc=paul@xen.org \
--cc=roman@zededa.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).