From: Julien Grall <julien.grall@arm.com>
To: Andrii Anisov <andrii_anisov@epam.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrii Anisov <andrii.anisov@gmail.com>
Subject: Re: Renesas R-Car Gen3 SoCs earlyprintk support.
Date: Thu, 6 Jul 2017 13:35:37 +0100 [thread overview]
Message-ID: <21eef9ec-aadb-4dbb-f5f1-76ebc56f1fd4@arm.com> (raw)
In-Reply-To: <bac4e897-1e01-67d9-614d-1807384f724d@epam.com>
Hi Andrii,
On 06/07/17 13:24, Andrii Anisov wrote:
> On 06.07.17 14:43, Julien Grall wrote:
>> Well, I would expect no changes in either in the BSP, kernel,
>> device-tree when you run with Xen.
> Even without adding XEN specific chosen node? Or you do not count it as
> a devtree change?
I don't count the chosen node. This could be done via the u-boot command
line, so no need to load a separate DT.
>
>>>> The wiki page gives the false impression that Xen upstream is fully
>>>> supported on Renesas, whilst from what you said this is not true and
>>>> change are required in the BSP.
>>> I would say in different words: XEN upstream is fully supported on
>>> Renesas, but due to XEN functionality gaps the BSP should be adjusted
>>> appropriately.
>>
>> You can't say in the same sentence, the board is fully supported and
>> there are missing functionality that requires change in the BSP. They
>> are incompatible.
>>
>> I agree that we are able to boot Xen on Renesas (not sure to which
>> extend without modification). But you can't claim it is fully
>> supported until all those gaps are fixed.
> Well...
> Do you say that calls to ARM TEE from XEN domains works for all
> supported boards? And smc trapping is somehow Renesas specific?
I am not aware of any board we currently support requiring to issue SMC
calls.
We used to have one in the past, but this has been fixed in the BSP to
avoid issuing SMC when it is not allowed.
> Or you state that TEE is never provided as a part of BSP for supported
> boards? So nobody mention the gap?
You are the first person looking actively at TEE with Xen upstream. I
personally don't have any board that is using TEE.
Are you saying TEE will not be detected via the Device Tree and the BSP
will always assume it is present?
> Maybe you claim BSP of all supported boards goes out of bootloader in
> Hypervisor mode/EL2? So no changes to FW/bootloader should be ever done
> for supported boards?
If the bootloader does not leave you in EL2, then it is a bug in the
bootloader that should be fixed in the official BSP. Not in a separate
repository just for Xen.
My point is we should work with Renesas to get the official BSP to
support Xen rather than forking the BSP and carry all the changes.
This is more sustainable and less overhead for everyone in the future.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-06 12:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 16:29 Renesas R-Car Gen3 SoCs earlyprintk support Andrii Anisov
2017-07-05 16:29 ` [PATCH 1/2] xen:arm64: Add SCIF UART support for earlyprintk Andrii Anisov
2017-07-26 15:25 ` Andrii Anisov
2017-07-26 15:33 ` Julien Grall
2017-07-26 15:39 ` Andrii Anisov
2017-07-05 16:29 ` [PATCH 2/2] xen:arm: earlyprintk configuration for R-Car Gen3 boards Andrii Anisov
2017-07-26 15:25 ` Andrii Anisov
2017-07-26 15:34 ` Julien Grall
2017-07-05 16:34 ` Renesas R-Car Gen3 SoCs earlyprintk support Julien Grall
2017-07-05 16:41 ` Andrii Anisov
2017-07-05 16:50 ` Julien Grall
2017-07-05 17:00 ` Andrii Anisov
2017-07-05 17:18 ` Julien Grall
2017-07-06 11:31 ` Andrii Anisov
2017-07-06 11:43 ` Julien Grall
2017-07-06 12:24 ` Andrii Anisov
2017-07-06 12:35 ` Julien Grall [this message]
2017-07-07 10:47 ` Andrii Anisov
2017-07-07 10:55 ` Julien Grall
2017-07-07 12:11 ` Andrii Anisov
2017-07-14 17:00 ` 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=21eef9ec-aadb-4dbb-f5f1-76ebc56f1fd4@arm.com \
--to=julien.grall@arm.com \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.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).