From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrii Anisov <andrii.anisov@globallogic.com>
Subject: Re: [PATCH v2 3/3] xen/arm: Enable switch to hyp mode
	for OMAP5432
Date: Thu, 15 Aug 2013 17:51:06 +0300
Message-ID: <CAGQvs6hfu-QgPeCmKcv-vx9nTHNCPsh1AJQ18PSQtQNPkGZ_uw@mail.gmail.com>
References: <1376572790-27724-1-git-send-email-baozich@gmail.com>
	<1376572790-27724-4-git-send-email-baozich@gmail.com>
	<CAGQvs6gd-oR3-=p22-r30-BApKB51rBgDM_bAUz=nrrZQbVaXA@mail.gmail.com>
	<CAGQvs6irwsh-s6=cPwapiY2ZNRdYqNXc5ytvqEm2QvZXjz-vHQ@mail.gmail.com>
	<CAGQvs6hVpmWL-221GVmn1Dz8dGqpHAcZWzZ_c68jY62SYaUCdw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4752906744092373291=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAGQvs6hVpmWL-221GVmn1Dz8dGqpHAcZWzZ_c68jY62SYaUCdw@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
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>
List-Id: xen-devel@lists.xenproject.org

--===============4752906744092373291==
Content-Type: multipart/alternative; boundary=f46d043c815e9c24f904e3fd9a01

--f46d043c815e9c24f904e3fd9a01
Content-Type: text/plain; charset=ISO-8859-1

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.
>

--f46d043c815e9c24f904e3fd9a01
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Well,<div><br></div><div>My colleague just gave me a nasty=
 hint.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex">
<span style=3D"font-family:arial,sans-serif;font-size:13px">Code CPU1 is ki=
cked to, does switch to HYP, and executes what ROM<br></span><span style=3D=
"font-family:arial,sans-serif;font-size:13px">normally does: wait for event=
, checks AUX_CORE_BOOT_0 if ok - jumps to<br>
</span><span style=3D"font-family:arial,sans-serif;font-size:13px">AUX_CORE=
_BOOT_1. The only difference from waiting in ROM code is that<br></span><sp=
an style=3D"font-family:arial,sans-serif;font-size:13px">CPU1 is already in=
 HYP.</span></blockquote>
<div class=3D"gmail_extra">Another difference is that executed wait/check c=
ode is placed not in ROM but in RAM. And, theoretically, could be corrupted=
.</div><div class=3D"gmail_extra">Taking in account existing plans to move =
CPU kicking to later stages, f.e. while xen parses dt.</div>
<div class=3D"gmail_extra"><div><br></div><div><font face=3D"Arial"><span s=
tyle=3D"font-size:12px"><b>Sincerely,</b></span></font></div><div><font fac=
e=3D"Arial"><span style=3D"font-size:12px"><b>Andrii Anisov.</b></span></fo=
nt></div>

<br><br><div class=3D"gmail_quote">On Thu, Aug 15, 2013 at 5:27 PM, Andrii =
Anisov <span dir=3D"ltr">&lt;<a href=3D"mailto:andrii.anisov@globallogic.co=
m" target=3D"_blank">andrii.anisov@globallogic.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
Well,<br>
<br>
Providing mode_switch.c going to be removed, this discussion is just<br>
theorization ;)<br>
<br>
Sincerely,<br>
Andrii Anisov.<br>
</blockquote></div><br></div></div>

--f46d043c815e9c24f904e3fd9a01--


--===============4752906744092373291==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============4752906744092373291==--