Hi Jonathan,
Welcome to China and thanks for the detailed update!
@Rob,Mark
Welcome to join LOD discussion!
For Jonathan’s first topics:
How to do device tree representation of multi thread cores and resulting shared L1 caches.
Would you like to communicate in this email list or do we need a LOD meeting to reach an agreement?
@James,
For the MPAM upstream,any help needed for the upstream from Huawei or Linaro?
Thanks:)
Joyce
> On 21 Feb 2025, at 18:07, Jonathan Cameron <Jonathan.Cameron(a)huawei.com> wrote:
>
>
> Hi Joyce,
>
> I'll be in Shenzhen next week but should be able to dial in subject to
> overcoming a slightly different network.
>
> If we can poke the following disconnect that would be very helpful
> - if it happens on list rather than needing to be discussed on the call
> that's absolutely fine.
>
> It's a difference of opinion between Mark Rutland and Rob Herring
> (both ARM) about how to do device tree representation of multi thread
> cores and resulting shared L1 caches. We mostly care about this because
> we'd like to maintain same level of support in QEMU for ACPI (which has
> always handled this case) and DT.
>
> This was try number 1 based on advice from Rob was to use multiple reg
> entries in a single cpu node (how the DT spec currently specifies it
> based on ancient power PC roots)
>
> https://lore.kernel.org/linux-arm-kernel/20250110161057.445-1-alireza.sanae…
> Mark suggested that we just do out of CPU node description as is done for every
> other level of cache because of the complexity of phandles pointing to the
> node.
>
> Proposal of out of CPU node description. Rob not happy with this one.
> https://lore.kernel.org/all/20250129164855.676-1-alireza.sanaee@huawei.com/
> https://lore.kernel.org/all/20250203120527.3534-1-alireza.sanaee@huawei.com/
>
> Whilst I'm fairly sure Mark's concerns about references to the CPU node can
> be resolved with a few minor tweaks (a few properties may become arrays that
> are index rather than single element) we'd really like to have the two
> experts engaged in the same thread as so far it's been a case of alternate
> responses.
>
> The other topic that is in my pile is the cache flushing by PA range work.
> I'm going to be working with our HQ team to ensure the design we put out
> for that is general enough over the next 2 weeks so we should have something
> to share after that. The remaining questions prior to posting an RFC are
> all low level detail things that I don't think would benefit from a discussion
> until we've shown the code.
>
> Final potential topic is MPAM. Particularly if there is anything specific
> we can do to help with upstreaming.
>
> Jonathan
>
>
> Joyce Qi <joyce.qi(a)linaro.org> wrote:
>
>> Hi Jonathan, all,
>>
>> Happy New Year to all!
>>
>> Do we have any topic to sync next week?
>>
>> Thanks:)
>> Joyce
>>
>>
>>
>>
>>> On 27 Nov 2024, at 08:00, linaro-open-discussions-request(a)op-lists.linaro.org wrote:
>>>
>>> Send Linaro-open-discussions mailing list submissions to
>>> linaro-open-discussions(a)op-lists.linaro.org
>>>
>>> To subscribe or unsubscribe via email, send a message with subject or
>>> body 'help' to
>>> linaro-open-discussions-request(a)op-lists.linaro.org
>>>
>>> You can reach the person managing the list at
>>> linaro-open-discussions-owner(a)op-lists.linaro.org
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Linaro-open-discussions digest..."
>>>
>>> Today's Topics:
>>>
>>> 1. Re: Flush by PA range Designs. (was Re: Linaro-open-discussions Digest, Vol 38, Issue 14)
>>> (Joyce Qi)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Tue, 26 Nov 2024 18:36:22 +0800
>>> From: Joyce Qi <joyce.qi(a)linaro.org>
>>> Subject: [Linaro-open-discussions] Re: Flush by PA range Designs.
>>> (was Re: Linaro-open-discussions Digest, Vol 38, Issue 14)
>>> To: James Morse <james.morse(a)arm.com>
>>> Cc: Jonathan Cameron <Jonathan.Cameron(a)Huawei.com>, James Morse via
>>> Linaro-open-discussions <linaro-open-discussions(a)op-lists.linaro.org>,
>>> linuxarm(a)huawei.com, zengheng4(a)huawei.com, wangyushan12(a)huawei.com,
>>> Dave Martin <Dave.Martin(a)arm.com>
>>> Message-ID: <5BF890F5-CE52-4682-AFE6-9FBDE56F2247(a)linaro.org>
>>> Content-Type: text/plain; charset=utf-8
>>>
>>> Hi all,
>>>
>>> Will cancel today’s meeting since no special topic today, welcome to contact with when needed.
>>>
>>> Thanks
>>> Joyce
>>>
>>>> On 25 Nov 2024, at 21:01, Joyce Qi <joyce.qi(a)linaro.org> wrote:
>>>>
>>>> Hi Jonathan,
>>>>
>>>> Would you like to continue the MPAM, Flush by PA range Designs or any other topics during tomorrow’s LOD meeting?
>>>>
>>>> Thanks
>>>> Joyce
>>>>
>>>>
>>>>> On 24 Oct 2024, at 00:14, James Morse <james.morse(a)arm.com> wrote:
>>>>>
>>>>> Hi guys,
>>>>>
>>>>> (CC: +Dave Martin)
>>>>>
>>>>> On 10/21/24 15:01, Joyce Qi wrote:
>>>>>>> On 21 Oct 2024, at 20:50, James Morse <james.morse(a)arm.com> wrote:
>>>>>>> On 21/10/2024 11:00, Joyce Qi via Linaro-open-discussions wrote:
>>>>>>>> Thanks a lot for the detailed description and document sharing.
>>>>>>>> I have uploaded the MPAM materials to the LOD Confluence.
>>>>>>>>
>>>>>>>> https://linaro.atlassian.net/wiki/spaces/LOD/overview
>>>>>
>>>>>>>> Are you available to join tomorrow’s LoD meeting for the MPAM topics ?
>>>>>
>>>>> The code already published for something like the intPARTID proposal is here:
>>>>> https://git.gitlab.arm.com/linux-arm/linux-dm/-/commits/mpam/partid-pmg-rem…
>>>>>
>>>>> The aim was to keep it within the MPAM driver, initially based on some static configuration to prove
>>>>> its useful before making it more dynamic, probably a mount option.
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> James
>>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> Linaro-open-discussions mailing list -- linaro-open-discussions(a)op-lists.linaro.org
>>> To unsubscribe send an email to linaro-open-discussions-leave(a)op-lists.linaro.org
>>>
>>>
>>> ------------------------------
>>>
>>> End of Linaro-open-discussions Digest, Vol 50, Issue 1
>>> ******************************************************
>>
>
Hi Jonathan, all,
Happy New Year to all!
Do we have any topic to sync next week?
Thanks:)
Joyce
> On 27 Nov 2024, at 08:00, linaro-open-discussions-request(a)op-lists.linaro.org wrote:
>
> Send Linaro-open-discussions mailing list submissions to
> linaro-open-discussions(a)op-lists.linaro.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> linaro-open-discussions-request(a)op-lists.linaro.org
>
> You can reach the person managing the list at
> linaro-open-discussions-owner(a)op-lists.linaro.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linaro-open-discussions digest..."
>
> Today's Topics:
>
> 1. Re: Flush by PA range Designs. (was Re: Linaro-open-discussions Digest, Vol 38, Issue 14)
> (Joyce Qi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 26 Nov 2024 18:36:22 +0800
> From: Joyce Qi <joyce.qi(a)linaro.org>
> Subject: [Linaro-open-discussions] Re: Flush by PA range Designs.
> (was Re: Linaro-open-discussions Digest, Vol 38, Issue 14)
> To: James Morse <james.morse(a)arm.com>
> Cc: Jonathan Cameron <Jonathan.Cameron(a)Huawei.com>, James Morse via
> Linaro-open-discussions <linaro-open-discussions(a)op-lists.linaro.org>,
> linuxarm(a)huawei.com, zengheng4(a)huawei.com, wangyushan12(a)huawei.com,
> Dave Martin <Dave.Martin(a)arm.com>
> Message-ID: <5BF890F5-CE52-4682-AFE6-9FBDE56F2247(a)linaro.org>
> Content-Type: text/plain; charset=utf-8
>
> Hi all,
>
> Will cancel today’s meeting since no special topic today, welcome to contact with when needed.
>
> Thanks
> Joyce
>
>> On 25 Nov 2024, at 21:01, Joyce Qi <joyce.qi(a)linaro.org> wrote:
>>
>> Hi Jonathan,
>>
>> Would you like to continue the MPAM, Flush by PA range Designs or any other topics during tomorrow’s LOD meeting?
>>
>> Thanks
>> Joyce
>>
>>
>>> On 24 Oct 2024, at 00:14, James Morse <james.morse(a)arm.com> wrote:
>>>
>>> Hi guys,
>>>
>>> (CC: +Dave Martin)
>>>
>>> On 10/21/24 15:01, Joyce Qi wrote:
>>>>> On 21 Oct 2024, at 20:50, James Morse <james.morse(a)arm.com> wrote:
>>>>> On 21/10/2024 11:00, Joyce Qi via Linaro-open-discussions wrote:
>>>>>> Thanks a lot for the detailed description and document sharing.
>>>>>> I have uploaded the MPAM materials to the LOD Confluence.
>>>>>>
>>>>>> https://linaro.atlassian.net/wiki/spaces/LOD/overview
>>>
>>>>>> Are you available to join tomorrow’s LoD meeting for the MPAM topics ?
>>>
>>> The code already published for something like the intPARTID proposal is here:
>>> https://git.gitlab.arm.com/linux-arm/linux-dm/-/commits/mpam/partid-pmg-rem…
>>>
>>> The aim was to keep it within the MPAM driver, initially based on some static configuration to prove
>>> its useful before making it more dynamic, probably a mount option.
>>>
>>>
>>> Thanks,
>>>
>>> James
>>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> Linaro-open-discussions mailing list -- linaro-open-discussions(a)op-lists.linaro.org
> To unsubscribe send an email to linaro-open-discussions-leave(a)op-lists.linaro.org
>
>
> ------------------------------
>
> End of Linaro-open-discussions Digest, Vol 50, Issue 1
> ******************************************************
Hi,
Tomorrow, Tuesday, it's time for another LOC monthly meeting. For time
and connection details see the calendar at
https://www.trustedfirmware.org/meetings/
The TA-specific parts of fTPM have now been included in the first
OP-TEE release in the optee_ftpm and we run fTPM in the OP-TEE OS CI
loop at Github. Much of what we set out to do over half a year ago has
been done, but there are some issues with the quality of the code. It
doesn't compile without warnings and the coding style is inconsistent
with the normal OP-TEE coding style (or anything else). Let's discuss
how we can improve the status.
Are there any other topics?
Thanks,
Jens
Hi Jonathan,all
Do you have any topic to sync next Tuesday?
Since it is Christmas next week,we can put off the meeting after the holiday whenever you want to sync.
Thanks
Joyce
> 在 2023年11月29日,08:00,linaro-open-discussions-request@op-lists.linaro.org 写道:
>
> Send Linaro-open-discussions mailing list submissions to
> linaro-open-discussions(a)op-lists.linaro.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> linaro-open-discussions-request(a)op-lists.linaro.org
>
> You can reach the person managing the list at
> linaro-open-discussions-owner(a)op-lists.linaro.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linaro-open-discussions digest..."
>
> Today's Topics:
>
> 1. Re: [Request] Regarding non-RFC patch-set of Virtual CPU Hotplug kernel support
> (Joyce Qi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 28 Nov 2023 08:44:14 +0800
> From: Joyce Qi <joyce.qi(a)linaro.org>
> Subject: [Linaro-open-discussions] Re: [Request] Regarding non-RFC
> patch-set of Virtual CPU Hotplug kernel support
> To: Salil Mehta <salil.mehta(a)huawei.com>
> Cc: Jianyong Wu <Jianyong.Wu(a)arm.com>, Russell King
> <linux(a)armlinux.org.uk>, James Morse <James.Morse(a)arm.com>,
> "linaro-open-discussions(a)op-lists.linaro.org"
> <linaro-open-discussions(a)op-lists.linaro.org>, Lorenzo Pieralisi
> <lorenzo.pieralisi(a)linaro.org>, "karl.heubaum(a)oracle.com"
> <karl.heubaum(a)oracle.com>, "darren(a)os.amperecomputing.com"
> <darren(a)os.amperecomputing.com>, "ilkka(a)os.amperecomputing.com"
> <ilkka(a)os.amperecomputing.com>, "miguel.luis(a)oracle.com"
> <miguel.luis(a)oracle.com>, "vishnu(a)os.amperecomputing.com"
> <vishnu(a)os.amperecomputing.com>, Linuxarm <linuxarm(a)huawei.com>,
> "salil.mehta(a)opnsrc.net" <salil.mehta(a)opnsrc.net>
> Message-ID: <764691EE-1EA6-4245-8D92-434B0CD3BBC4(a)linaro.org>
> Content-Type: text/plain; charset=gb2312
>
> Hi all,
>
> Will cancel today’s meeting since the “Regarding non-RFC patch-set of Virtual CPU Hotplug kernel support” can be continually discussed in the LOD mail list.
>
> Thanks:)
> Joyce
>
>> 在 2023年11月27日,17:50,Salil Mehta <salil.mehta(a)huawei.com> 写道:
>>
>> Hi Joyce,
>> I have do not have any.
>>
>> Thanks
>> Salil
>> From: Joyce Qi <joyce.qi(a)linaro.org <mailto:joyce.qi@linaro.org>>
>> Sent: Sunday, November 26, 2023 11:51 AM
>> To: Jianyong Wu <Jianyong.Wu(a)arm.com <mailto:Jianyong.Wu@arm.com>>
>> Cc: Russell King <linux(a)armlinux.org.uk <mailto:linux@armlinux.org.uk>>; James Morse <James.Morse(a)arm.com <mailto:James.Morse@arm.com>>; Salil Mehta <salil.mehta(a)huawei.com <mailto:salil.mehta@huawei.com>>; linaro-open-discussions(a)op-lists.linaro.org <mailto:linaro-open-discussions@op-lists.linaro.org>; Lorenzo Pieralisi <lorenzo.pieralisi(a)linaro.org <mailto:lorenzo.pieralisi@linaro.org>>; karl.heubaum(a)oracle.com <mailto:karl.heubaum@oracle.com>; darren(a)os.amperecomputing.com <mailto:darren@os.amperecomputing.com>; ilkka(a)os.amperecomputing.com <mailto:ilkka@os.amperecomputing.com>; miguel.luis(a)oracle.com <mailto:miguel.luis@oracle.com>; vishnu(a)os.amperecomputing.com <mailto:vishnu@os.amperecomputing.com>; Linuxarm <linuxarm(a)huawei.com <mailto:linuxarm@huawei.com>>; salil.mehta(a)opnsrc.net <mailto:salil.mehta@opnsrc.net>; Jonathan Cameron <jonathan.cameron(a)huawei.com <mailto:jonathan.cameron@huawei.com>>
>> Subject: Re: [Linaro-open-discussions] Re: [Request] Regarding non-RFC patch-set of Virtual CPU Hotplug kernel support
>>
>> Hi all,
>>
>> Do we have topic to sync next Tuesday?
>>
>> Thanks
>> Joyce
>>
>>
>> 在 2023年11月22日,09:22,Jianyong Wu <Jianyong.Wu(a)arm.com <mailto:Jianyong.Wu@arm.com>> 写道:
>>
>>
>>
>>
>> -----Original Message-----
>> From: Russell King <linux(a)armlinux.org.uk <mailto:linux@armlinux.org.uk>>
>> Sent: 2023年11月21日 17:45
>> To: Jianyong Wu <Jianyong.Wu(a)arm.com <mailto:Jianyong.Wu@arm.com>>
>> Cc: James Morse <James.Morse(a)arm.com <mailto:James.Morse@arm.com>>; salil.mehta(a)huawei.com <mailto:salil.mehta@huawei.com>;
>> linaro-open-discussions(a)op-lists.linaro.org <mailto:linaro-open-discussions@op-lists.linaro.org>; Joyce Qi <joyce.qi(a)linaro.org <mailto:joyce.qi@linaro.org>>;
>> Lorenzo Pieralisi <lorenzo.pieralisi(a)linaro.org <mailto:lorenzo.pieralisi@linaro.org>>; karl.heubaum(a)oracle.com <mailto:karl.heubaum@oracle.com>;
>> darren(a)os.amperecomputing.com <mailto:darren@os.amperecomputing.com>; ilkka(a)os.amperecomputing.com <mailto:ilkka@os.amperecomputing.com>;
>> miguel.luis(a)oracle.com <mailto:miguel.luis@oracle.com>; vishnu(a)os.amperecomputing.com <mailto:vishnu@os.amperecomputing.com>; Linuxarm
>> <linuxarm(a)huawei.com <mailto:linuxarm@huawei.com>>; salil.mehta(a)opnsrc.net <mailto:salil.mehta@opnsrc.net>
>> Subject: Re: [Linaro-open-discussions] Re: [Request] Regarding non-RFC
>> patch-set of Virtual CPU Hotplug kernel support
>>
>> On Fri, Nov 03, 2023 at 09:41:36AM +0000, Jianyong Wu wrote:
>>
>> Also, I have a plan to add an integration test CI in kata community for Vcpu
>> Hotplug on Arm. There we can do more tests integrating with k8s. To do the test,
>> I need a stable git link of Kernel and Qemu including the latest change, thus, I
>> can clone the code from a fixed source in each test. It's very helpful if you guys
>> could aid.
>>
>> I don't think I properly replied to this. I think what you want is not a "stable" git
>> tree, but a branch that you can pull that always contains the latest code.
>>
>> For my tree, that will be:
>>
>> git.armlinux.org.uk/~rmk/linux-arm.git <http://git.armlinux.org.uk/~rmk/linux-arm.git> aarch64/hotplug-vcpu/head
>>
>> which will be regularly kept updated and rebased against the mainline kernel. It
>> may sometimes be between releases rather than based on -rc or final kernels.
>>
>>
>> Great! That's what I want.
>>
>>
>> Does that satisfy your need?
>>
>> Yes. Thanks Russell. It saves me lots of work.
>>
>> Thanks
>> Jianyong
>>
>>
>> Thanks.
>>
>> --
>> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ <https://www.armlinux.org.uk/developer/patches/>
>> FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
>> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> Linaro-open-discussions mailing list -- linaro-open-discussions(a)op-lists.linaro.org
> To unsubscribe send an email to linaro-open-discussions-leave(a)op-lists.linaro.org
>
>
> ------------------------------
>
> End of Linaro-open-discussions Digest, Vol 38, Issue 14
> *******************************************************
Hi,
Tomorrow, Tuesday, it's time for another LOC monthly meeting. For time
and connection details see the calendar at
https://www.trustedfirmware.org/meetings/
I've started the Pull Request
https://github.com/OP-TEE/optee_os/pull/7054 to import the TA-specific
part of fTPM into the OP-TEE git.
It appears that MS has filed for patents on fTPM. How does that affect
downstream usage? Would it be safer or more convenient for downstream
if the fTPM TA was in a separate git instead of the optee_os git?
Are there any other topics?
Thanks,
Jens
Hi,
Tomorrow, Tuesday, it's time for another LOC monthly meeting. For time
and connection details see the calendar at
https://www.trustedfirmware.org/meetings/
I've started to work on importing the TA specific part of fTPM into
the OP-TEE git, based on the patches published at
https://github.com/zeschg/ms-tpm-20-ref/tree/feat_add_tee_crypto
replacing the third-party crypto library with TEE Internal core API.
I'd appreciate help reviewing this when I publish the work.
We'll need a way to test that the imported fTPM implementation works
as expected, preferably something we can have in our CI loop.
Are there any other topics?
Cheers,
Jens