All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Andrii Anisov <andrii.anisov@globallogic.com>
Cc: Iurii Konovalenko <iurii.konovalenko@globallogic.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v1 1/2] arm: Add ability to relocate Xen in over 4GB space
Date: Fri, 10 Apr 2015 15:49:42 +0100	[thread overview]
Message-ID: <5527E306.10104@citrix.com> (raw)
In-Reply-To: <CAGQvs6gj4LmvX9HN_yYKJR1y-eMgzE0ph67PLT3o=wi8gjaXRw@mail.gmail.com>

On 10/04/15 15:38, Andrii Anisov wrote:
> Julien,
> 
>>> Secondary CPUs run on unrelocated copy of Xen until turning on MMU.
>>> After turning on MMU secondary CPUs run on relocated copy of Xen.
>>
>> The non-relocated copy of Xen is not marked as reserved. So Xen may
>> allocate the area for his own purpose before the secondary CPU has boot.
> 
> Could you please clarify how the same issue resolved with the piece of
> bootloader code which implements secondary processors wfe in HYP mode
> and jump to hypervisor?

I'm not sure to understand the question.

Currently, Xen add a bootmodule  (see start_xen) to cover Xen. The base
address is updated once Xen is relocated.

You may want to add a bootmodule for the non-relocated Xen.

I hope it answers to your question.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-04-10 14:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 12:36 [PATCH v1 0/2] relocate Xen in over 4GB space for arm32 Iurii Konovalenko
2015-04-08 12:36 ` [PATCH v1 1/2] arm: Add ability to relocate Xen in over 4GB space Iurii Konovalenko
2015-04-08 16:05   ` Julien Grall
2015-04-08 17:24     ` Andrii Anisov
2015-04-08 17:25       ` Andrii Anisov
2015-05-08 16:02       ` Ian Campbell
2015-04-10 13:58     ` Iurii Konovalenko
2015-04-10 14:25       ` Julien Grall
2015-04-14 11:00         ` Ian Campbell
2015-04-10 14:38     ` Andrii Anisov
2015-04-10 14:49       ` Julien Grall [this message]
2015-04-16 12:59         ` Ian Campbell
2015-04-15 16:29     ` Ian Campbell
2015-04-15 16:41   ` Ian Campbell
2015-04-08 12:36 ` [PATCH v1 2/2] arm: skip verifying memory continuity Iurii Konovalenko
2015-04-08 16:20   ` Julien Grall

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=5527E306.10104@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=andrii.anisov@globallogic.com \
    --cc=ian.campbell@citrix.com \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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 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.