On 2024/12/26 15:18, Shrikanth Hegde wrote:
>
>
> On 12/20/24 13:23, Yicong Yang wrote:
>> From: Yicong Yang
>>
>> Currently if architectures want to support HOTPLUG_SMT they need to
>> provide a topology_is_primary_thread() telling the framework which
>> thread in the SMT cannot offline. Howeve
On 12/20/24 13:23, Yicong Yang wrote:
From: Yicong Yang
Currently if architectures want to support HOTPLUG_SMT they need to
provide a topology_is_primary_thread() telling the framework which
thread in the SMT cannot offline. However arm64 doesn't have a
restriction on which thread in the SMT
On 2024/12/24 0:34, Jonathan Cameron wrote:
> On Fri, 20 Dec 2024 15:59:27 +0800
> Yicong Yang wrote:
>
>> On 2024/12/20 15:53, Yicong Yang wrote:
>>> From: Yicong Yang
>>>
>>> Currently if architectures want to support HOTPLUG_SMT they need to
>>> provide a topology_is_primary_thread() telling
On Fri, 20 Dec 2024 15:59:27 +0800
Yicong Yang wrote:
> On 2024/12/20 15:53, Yicong Yang wrote:
> > From: Yicong Yang
> >
> > Currently if architectures want to support HOTPLUG_SMT they need to
> > provide a topology_is_primary_thread() telling the framework which
> > thread in the SMT cannot o
On 2024/12/20 15:53, Yicong Yang wrote:
> From: Yicong Yang
>
> Currently if architectures want to support HOTPLUG_SMT they need to
> provide a topology_is_primary_thread() telling the framework which
> thread in the SMT cannot offline. However arm64 doesn't have a
> restriction on which thread i
From: Yicong Yang
Currently if architectures want to support HOTPLUG_SMT they need to
provide a topology_is_primary_thread() telling the framework which
thread in the SMT cannot offline. However arm64 doesn't have a
restriction on which thread in the SMT cannot offline, a simplest
choice is that
