xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Anisov <andrii.anisov@globallogic.com>
To: Chen Baozi <baozich@gmail.com>
Cc: Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 3/3] xen/arm: Enable switch to hyp mode for OMAP5432
Date: Thu, 15 Aug 2013 17:51:06 +0300	[thread overview]
Message-ID: <CAGQvs6hfu-QgPeCmKcv-vx9nTHNCPsh1AJQ18PSQtQNPkGZ_uw@mail.gmail.com> (raw)
In-Reply-To: <CAGQvs6hVpmWL-221GVmn1Dz8dGqpHAcZWzZ_c68jY62SYaUCdw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 761 bytes --]

Well,

My colleague just gave me a nasty hint.

Code CPU1 is kicked to, does switch to HYP, and executes what ROM
> normally does: wait for event, checks AUX_CORE_BOOT_0 if ok - jumps to
> AUX_CORE_BOOT_1. The only difference from waiting in ROM code is that
> CPU1 is already in HYP.

Another difference is that executed wait/check code is placed not in ROM
but in RAM. And, theoretically, could be corrupted.
Taking in account existing plans to move CPU kicking to later stages, f.e.
while xen parses dt.

*Sincerely,*
*Andrii Anisov.*


On Thu, Aug 15, 2013 at 5:27 PM, Andrii Anisov <
andrii.anisov@globallogic.com> wrote:

> Well,
>
> Providing mode_switch.c going to be removed, this discussion is just
> theorization ;)
>
> Sincerely,
> Andrii Anisov.
>

[-- Attachment #1.2: Type: text/html, Size: 1805 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-08-15 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 13:19 [PATCH v2 0/3] Specific mapping for dom0, smp kick cpus and hyp mode switch for OMAP5 Chen Baozi
2013-08-15 13:19 ` [PATCH v2 1/3] xen/arm: Specific mapping for dom0 on OMAP5 platform Chen Baozi
2013-08-22 10:21   ` Ian Campbell
2013-08-22 12:54     ` Ian Campbell
2013-08-23  0:04       ` Chen Baozi
2013-08-15 13:19 ` [PATCH v2 2/3] xen/arm: Support kick_cpus for OMAP5 Chen Baozi
2013-08-15 14:12   ` Andrii Anisov
2013-08-16  2:04     ` Chen Baozi
2013-08-15 13:19 ` [PATCH v2 3/3] xen/arm: Enable switch to hyp mode for OMAP5432 Chen Baozi
2013-08-15 14:09   ` Andrii Anisov
2013-08-15 14:25     ` Andrii Anisov
2013-08-15 14:27       ` Andrii Anisov
2013-08-15 14:51         ` Andrii Anisov [this message]
2013-08-15 14:37     ` Chen Baozi
2013-08-15 14:42       ` Andrii Anisov

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=CAGQvs6hfu-QgPeCmKcv-vx9nTHNCPsh1AJQ18PSQtQNPkGZ_uw@mail.gmail.com \
    --to=andrii.anisov@globallogic.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=baozich@gmail.com \
    --cc=julien.grall@linaro.org \
    --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 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).