Hi Oleksii,
On 25/06/2025 20:47, Oleksii Moisieiev wrote:
On 23/06/2025 11:02, Julien Grall wrote:
I am probably missing something. But it looks like TF-A requires to
suport multi-agent so Xen can use it. Am I correct?
Furthermore, I can't tell why the multi-agent support is Xen specific.
Surely, you may want something similar with other hypervisors? If not,
then my next question is why does Xen needs to do things differently?
Cheers,
Yes, multi-agent support is required in TF-A for Xen, but this is not
specific to Xen.
I am really confused. If the support is not Xen specific then why do we
end up to have xen specific node/properties in your proposal (see [1])
such as xen,scmi-secondary-agents.
I also question the placement of the SMCI multi-agent in /chosen. For me
/chosen is for configuration related to the hypervisor/OS. But here, it
seems the multi-agent SMCI is related to the platform.
So wouldn't it be better to create a new compatible arm,smci-multi that
will include the information for multi? An alternative would be to
extend the existing SCMI node in a backward compatible way.
Lastly, I see if you put a node under "/chosen" with "arm,scmi-smc".
Have you checked this will not confused Linux? I was under the
impression Linux would look for any node with the compatible when
initializing a driver.
Cheers,
[1]
https://lists.xenproject.org/archives/html/xen-devel/2025-06/msg01421.html
--
Julien Grall
