Hi Jonathan，all
Are there any items that need to sync during next Tue's LOD meeting？
Thanks
Joyce
> On 26 Mar 2025, 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. About the Device tree handling multiple threads in ARM cpu node LOD discussion(Linaro Open Discussion)
> (Joyce Qi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 25 Mar 2025 19:24:43 +0800
> From: Joyce Qi <joyce.qi(a)linaro.org>
> Subject: [Linaro-open-discussions] About the Device tree handling
> multiple threads in ARM cpu node LOD discussion(Linaro Open
> Discussion)
> To: Jonathan Cameron <jonathan.cameron(a)huawei.com>
> Cc: Joyce Qi <joyce.qi(a)linaro.org>,
> linaro-open-discussions(a)op-lists.linaro.org, Lorenzo Pieralisi
> <lorenzo.pieralisi(a)linaro.org>, James Morse <james.morse(a)arm.com>, Rob
> Herring <robh(a)kernel.org>, Mark Rutland <mark.rutland(a)arm.com>,
> Alireza Sanaee <alireza.sanaee(a)huawei.com>
> Message-ID: <EB0D6409-56E1-4749-9BCA-26D207EB5DE7(a)linaro.org>
> Content-Type: text/plain; charset=utf-8
>
> Hi Mark, Rob,
>
> https://lore.kernel.org/linux-arm-kernel/20250110161057.445-1-alireza.sanae… to the LoD discussion email list!
> Maybe you have missed the formal email since the title is not so clear:)
>
> Jonathan from Huawei wants to sync the about how to do device tree representation of multi thread cores and resulting shared L1 caches
> In this email list.
>
> Can we discuss here to have a unified solution?
>
>
> https://lore.kernel.org/linux-arm-kernel/20250110161057.445-1-alireza.sanae…
>
>
> Great 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
>>>> ******************************************************
>>>
>>
>
>
> ------------------------------
>
> 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 54, Issue 4
> ******************************************************
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/
OP-TEE version 4.6.0 was released on April 25.
Amir posted a v4 [1] of the QTEE driver. Sumit and I have spent quite
a bit of time reviewing this, but it would be welcome with comments
from others, too. For instance, for "tee: add
TEE_IOCTL_PARAM_ATTR_TYPE_UBUF" which adds yet another type of memory
reference.
optee_ftpm Issue "Warning in _plat__GetUnique()" [2], digging in this
reveals further issues.
[1] https://lore.kernel.org/lkml/20250428-qcom-tee-using-tee-ss-without-mem-obj…
[2] https://github.com/OP-TEE/optee_ftpm/issues/15
Are there any other topics?
Thanks,
Jens
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/
OP-TEE version 4.6.0 is expected to be released on Friday, April 25.
Since the 4.6.0-rc1 tag, we have merged a few small patches, but we
don't have any known issues that might block the release.
We discussed optee_ftpm briefly after that last release in January.
The code quality leaves a bit to be desired, with many warnings, an
inconsistent coding style, and possibly a few stubbed functions. How
can we improve the status?
Are there any other topics?
Thanks,
Jens
Hi James，Jonathan，
Do you have some update regarding Johantan’s email below and do we need to sync today？
Thanks
Joyce
> On 8 Mar 2025, 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: About next week LOD meeting topic collection
> (Jonathan Cameron)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 21 Feb 2025 10:07:03 +0000
> From: Jonathan Cameron <Jonathan.Cameron(a)huawei.com>
> Subject: [Linaro-open-discussions] Re: About next week LOD meeting
> topic collection
> To: Joyce Qi <joyce.qi(a)linaro.org>
> Cc: linaro-open-discussions(a)op-lists.linaro.org, Lorenzo Pieralisi
> <lorenzo.pieralisi(a)linaro.org>, James Morse <james.morse(a)arm.com>, Rob
> Herring <robh(a)kernel.org>, Mark Rutland <mark.rutland(a)arm.com>,
> Alireza Sanaee <alireza.sanaee(a)huawei.com>
> Message-ID: <20250221100703.000030b8(a)huawei.com>
> Content-Type: text/plain; charset="utf-8"
>
>
> 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
>>> ******************************************************
>>
>
>
> ------------------------------
>
> 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 53, Issue 3
> ******************************************************
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
