From: Andrii Anisov <Andrii_Anisov@epam.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Hunyue Yau <hy-gsoc@hy-research.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
Andre Przywara <andre.przywara@arm.com>,
Denis Obrezkov <denisobrezkov@gmail.com>,
Iain Hunter <drhunter95@gmail.com>,
"xen-users@lists.xenproject.org" <xen-users@lists.xenproject.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Starting to port xen on beagleboard-x15 (GSoC 2019 project)
Date: Tue, 18 Jun 2019 12:28:09 +0000 [thread overview]
Message-ID: <AM6PR03MB49190A0828A49569B64611B4E6EA0@AM6PR03MB4919.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <AM6PR0302MB3221D649900B54C2FFA7003A86EA0@AM6PR0302MB3221.eurprd03.prod.outlook.com>
+xen-devel
Hello Julien,
> I am a bit confused. Linux is able to bring-up CPU in hyp mode with the current
> U-boot. Why would we need more changes for Xen?
TI's ROM code starts all CPUs in NS PL1, doesn't matter if it is boot or secondary core.
If you look at Linux code [1], you'll see, that after the secondary core bringup Linux does switch that core from NS PL1 to PL2 (hyp mode) using ROM code interface (smc 0).
At some moment XEN dropped all to-hyp-mode switching code. So I did switch secondaries to hyp mode in u-boot with the loop which replicates the ROM Code logic in terms of waiting for an event and checking aux registers.
[1] https://elixir.bootlin.com/linux/v5.1/source/arch/arm/mach-omap2/omap-headsmp.S#L62
ANDRII ANISOV
Lead Systems Engineer
Office: +380 44 390 5457 x 66766 Cell: +380 50 573 8852 Email: andrii_anisov@epam.com
Kyiv, Ukraine (GMT+3) epam.com
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next parent reply other threads:[~2019-06-18 12:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <287117b9-952c-1a92-26e0-9597df936c27@gmail.com>
[not found] ` <cd936ab7-df65-1615-a03a-bea30b5814f9@arm.com>
[not found] ` <f3596bd5-ede3-7299-e28f-033ad32e6c99@gmail.com>
[not found] ` <62194faf-0bf8-61b8-a69f-e41934fb5a43@arm.com>
[not found] ` <0c900a15-14ab-9947-bffe-2fbeed176486@gmail.com>
[not found] ` <CALC81-vaVKgZoi27MauGTxjda8mchy5GRLipu5z=v1vh9fyvAg@mail.gmail.com>
[not found] ` <747dd124-3511-f010-dac7-b9b23d7b44ad@gmail.com>
[not found] ` <CALC81-tewzAtaaH94U1nVc-UiacR_YvqhaYcPXtXcviTFHAG8A@mail.gmail.com>
[not found] ` <ecb2cf41-51e5-2ff2-5e61-72be64399e40@arm.com>
[not found] ` <AM6PR0302MB32215CD7FAED139C682D92A386EA0@AM6PR0302MB3221.eurprd03.prod.outlook.com>
[not found] ` <ef82a028-9e4e-9976-d205-42cbc4bfc8ac@arm.com>
[not found] ` <AM6PR0302MB3221D649900B54C2FFA7003A86EA0@AM6PR0302MB3221.eurprd03.prod.outlook.com>
2019-06-18 12:28 ` Andrii Anisov [this message]
2019-06-18 12:54 ` [Xen-devel] Starting to port xen on beagleboard-x15 (GSoC 2019 project) Julien Grall
2019-06-18 13:27 ` Andrii Anisov
2019-06-18 13:47 ` Andrii Anisov
2019-06-18 16:19 ` Julien Grall
2019-06-19 12:01 ` Andrii Anisov
2019-06-19 14:33 ` Denis Obrezkov
2019-06-19 15:06 ` Julien Grall
2019-06-19 15:27 ` Andrii Anisov
2019-06-19 15:32 ` Julien Grall
2019-06-19 16:10 ` Andrii Anisov
2019-06-19 16:31 ` Julien Grall
2019-06-19 21:51 ` Denis Obrezkov
2019-06-19 22:08 ` Julien Grall
2019-06-19 22:06 ` Denis Obrezkov
2019-06-19 22:16 ` Julien Grall
2019-06-18 16:49 ` 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=AM6PR03MB49190A0828A49569B64611B4E6EA0@AM6PR03MB4919.eurprd03.prod.outlook.com \
--to=andrii_anisov@epam.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=andre.przywara@arm.com \
--cc=denisobrezkov@gmail.com \
--cc=drhunter95@gmail.com \
--cc=hy-gsoc@hy-research.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xen-users@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).