From: Julien Grall <julien@xen.org>
To: minyard@acm.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Roman Shaposhnik <roman@zededa.com>,
jeff.kubascik@dornerworks.com,
Julien Grall <julien.grall@arm.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: Troubles running Xen on Raspberry Pi 4 with 5.6.1 DomU
Date: Sat, 2 May 2020 18:48:27 +0100 [thread overview]
Message-ID: <ed02b555-dbaa-2ebf-d09f-0474e1a7a745@xen.org> (raw)
In-Reply-To: <20200502173529.GH9902@minyard.net>
On 02/05/2020 18:35, Corey Minyard wrote:
> On Sat, May 02, 2020 at 12:46:14PM +0100, Julien Grall wrote:
> No. If I am understanding this correctly, all the memory in dom0 below
> 1GB would have to be physically below 1GB.
Well, dom0 is directly mapped. In other word, dom0 physical address ==
host physical address. So if we allocate memory below 1GB in Xen, then
it will mapped below 1GB on dom0 as well.
The patch I suggested would try to allocate as much as possible memory
below 1GB. I believe this should do the trick for you here.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-05-02 17:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 2:20 Troubles running Xen on Raspberry Pi 4 with 5.6.1 DomU Roman Shaposhnik
2020-05-01 11:42 ` Corey Minyard
2020-05-02 1:06 ` Roman Shaposhnik
2020-05-02 2:16 ` Corey Minyard
2020-05-02 11:46 ` Julien Grall
2020-05-02 17:35 ` Corey Minyard
2020-05-02 17:48 ` Julien Grall [this message]
2020-05-04 12:44 ` Corey Minyard
2020-05-04 20:54 ` Roman Shaposhnik
2020-05-05 3:52 ` Stefano Stabellini
2020-05-05 5:36 ` Roman Shaposhnik
2020-05-05 22:34 ` Stefano Stabellini
2020-05-06 1:25 ` Boris Ostrovsky
2020-05-06 4:19 ` Roman Shaposhnik
2020-05-06 5:41 ` Jürgen Groß
2020-05-06 8:54 ` Peng Fan
2020-05-06 13:08 ` Nataliya Korovkina
2020-05-06 13:42 ` Boris Ostrovsky
2020-05-06 16:14 ` Nataliya Korovkina
2020-05-06 17:34 ` Stefano Stabellini
2020-05-06 21:12 ` Roman Shaposhnik
2020-05-13 0:33 ` Stefano Stabellini
2020-05-13 10:11 ` Julien Grall
2020-05-13 15:11 ` Stefano Stabellini
2020-05-13 18:19 ` Julien Grall
2020-05-13 18:26 ` Julien Grall
2020-05-13 19:51 ` Stefano Stabellini
2020-06-02 18:34 ` Corey Minyard
2020-06-02 19:24 ` Stefano Stabellini
2020-06-03 15:29 ` Corey Minyard
2020-06-03 15:37 ` Stefano Stabellini
2020-06-03 19:49 ` Corey Minyard
2020-06-03 19:55 ` Roman Shaposhnik
2020-05-13 19:13 ` Roman Shaposhnik
2020-05-13 19:49 ` Stefano Stabellini
2020-05-06 17:35 ` Boris Ostrovsky
2020-05-06 21:10 ` Roman Shaposhnik
2020-05-06 17:16 ` Stefano Stabellini
2020-05-06 17:32 ` Stefano Stabellini
2020-05-02 18:48 ` Elliott Mitchell
2020-05-02 19:43 ` Julien Grall
2020-05-06 13:48 ` Corey Minyard
2020-05-06 13:56 ` Julien Grall
2020-05-02 0:05 ` Stefano Stabellini
2020-05-02 1:12 ` Roman Shaposhnik
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=ed02b555-dbaa-2ebf-d09f-0474e1a7a745@xen.org \
--to=julien@xen.org \
--cc=jeff.kubascik@dornerworks.com \
--cc=julien.grall@arm.com \
--cc=minyard@acm.org \
--cc=roman@zededa.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.