[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5B3F18A4-5DA4-411E-9E26-7D25DEE3D414@arm.com>
Date: Thu, 11 Jun 2020 15:46:35 +0000
From: Achin Gupta <Achin.Gupta@....com>
To: Will Deacon <will@...nel.org>
CC: Rob Herring <robh@...nel.org>, Sudeep Holla <Sudeep.Holla@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Marc Zyngier <maz@...nel.org>, nd <nd@....com>
Subject: Re: [RFC PATCH 1/3] dt-bindings: Add ARM PSA FF binding for
non-secure VM partitions
Hi Will,
> On 10 Jun 2020, at 08:43, Will Deacon <will@...nel.org> wrote:
>
> On Tue, Jun 09, 2020 at 04:35:51PM -0600, Rob Herring wrote:
>> On Mon, Jun 01, 2020 at 10:45:10AM +0100, Sudeep Holla wrote:
>>> Add devicetree bindings for a Arm PSA FF-A compliant non-secure partition
>>> at virtual interface(VMs).
>>>
>>> Signed-off-by: Sudeep Holla <sudeep.holla@....com>
>>> ---
>>> .../devicetree/bindings/arm/arm,psa-ffa.txt | 47 +++++++++++++++++++
>>> 1 file changed, 47 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/arm/arm,psa-ffa.txt
>>
>> I'm hoping this goes away if the firmware is discoverable, but if not DT
>> bindings are DT schema now.
>
> We'll need the binding for the kvm host side, because there are plenty
> of partition properties that are not discoverable (e.g. number of vCPUs).
Just trying to understand the req. a bit better…
The FF-A driver in the host can use FFA_PARTITION_INFO_GET to determine the count of partitions and their vCPUs.
Is this about a guest being able to find out how many vCPUs it has?
Cheers,
Achin
>
> I'll have a go a yamlifying what I have...
>
> Will
>
Powered by blists - more mailing lists