From: Julien Grall <julien.grall@arm.com>
To: Andrii Anisov <andrii.anisov@gmail.com>,
Denis Obrezkov <denisobrezkov@gmail.com>
Cc: Hunyue Yau <hy-gsoc@hy-research.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Iain Hunter <drhunter95@gmail.com>,
Andre Przywara <andre.przywara@arm.com>,
Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
"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: Wed, 19 Jun 2019 16:32:56 +0100 [thread overview]
Message-ID: <04e2ff99-1276-a99b-b86c-825cf8cea858@arm.com> (raw)
In-Reply-To: <45406dbd-4aa1-8852-475e-1c37c93a7fa3@gmail.com>
Hi,
On 19/06/2019 16:27, Andrii Anisov wrote:
>
>
> On 19.06.19 18:06, Julien Grall wrote:
>> Lastly, please clean-up the code and send the patch on xen-devel. I will have
>> a closer look at that time. Feel free to ping me on IRC if you have any doubt
>> how to proceed.
>
> About the code: I think omap5_init_secondary() must be moved to the platform
> code (omap5.c).
Well omap5.c is C code... You can't call C in the boot process at least until
the MMU is on and we fully setup the processor.
Regarding the placement of the code, I am still split between two minds (either
head.S or a new specific .S for omap). However, this could be discussed once the
patch is submitted.
(Bear in mind this is likely the first time Denis works with the Xen community).
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-06-19 15:33 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 ` [Xen-devel] Starting to port xen on beagleboard-x15 (GSoC 2019 project) Andrii Anisov
2019-06-18 12:54 ` 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 [this message]
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=04e2ff99-1276-a99b-b86c-825cf8cea858@arm.com \
--to=julien.grall@arm.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=andre.przywara@arm.com \
--cc=andrii.anisov@gmail.com \
--cc=denisobrezkov@gmail.com \
--cc=drhunter95@gmail.com \
--cc=hy-gsoc@hy-research.com \
--cc=sstabellini@kernel.org \
--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 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).