On 2025/3/4 23:07, Pierre Gondois wrote:
>
>
> On 3/4/25 11:02, Sudeep Holla wrote:
>> On Tue, Mar 04, 2025 at 09:25:02AM +0100, Pierre Gondois wrote:
>>>
>>>
>>> On 3/3/25 15:40, Yicong Yang wrote:
On 2025/3/3 19:16, Sudeep Holla wrote:
> On Mon, Mar 03, 2025 at 10:56:12AM +0100, Pierre
On 3/4/25 11:02, Sudeep Holla wrote:
On Tue, Mar 04, 2025 at 09:25:02AM +0100, Pierre Gondois wrote:
On 3/3/25 15:40, Yicong Yang wrote:
On 2025/3/3 19:16, Sudeep Holla wrote:
On Mon, Mar 03, 2025 at 10:56:12AM +0100, Pierre Gondois wrote:
On 2/28/25 20:06, Sudeep Holla wrote:
Ditto as
On Tue, Mar 04, 2025 at 09:25:02AM +0100, Pierre Gondois wrote:
>
>
> On 3/3/25 15:40, Yicong Yang wrote:
> > On 2025/3/3 19:16, Sudeep Holla wrote:
> > > On Mon, Mar 03, 2025 at 10:56:12AM +0100, Pierre Gondois wrote:
> > > > On 2/28/25 20:06, Sudeep Holla wrote:
> > > > > > >
> > > > > > > Ditto
On 3/3/25 15:40, Yicong Yang wrote:
On 2025/3/3 19:16, Sudeep Holla wrote:
On Mon, Mar 03, 2025 at 10:56:12AM +0100, Pierre Gondois wrote:
On 2/28/25 20:06, Sudeep Holla wrote:
Ditto as previous patch, can get rid if it is default 1.
On non-SMT platforms, not calling cpu_smt_set_num_thr
On 2025/2/25 14:08, Hanjun Guo wrote:
> On 2025/2/18 22:10, Yicong Yang wrote:
>> From: Yicong Yang
>>
>> For ACPI we'll build the topology from PPTT and we cannot directly
>> get the SMT number of each core. Instead using a temporary xarray
>> to record the heterogeneous information (from ACPI_PP
On 2025/3/3 19:16, Sudeep Holla wrote:
> On Mon, Mar 03, 2025 at 10:56:12AM +0100, Pierre Gondois wrote:
>> On 2/28/25 20:06, Sudeep Holla wrote:
>
> Ditto as previous patch, can get rid if it is default 1.
>
On non-SMT platforms, not calling cpu_smt_set_num_threads() leaves
>
On Mon, Mar 03, 2025 at 10:56:12AM +0100, Pierre Gondois wrote:
> On 2/28/25 20:06, Sudeep Holla wrote:
> > > >
> > > > Ditto as previous patch, can get rid if it is default 1.
> > > >
> > >
> > > On non-SMT platforms, not calling cpu_smt_set_num_threads() leaves
> > > cpu_smt_num_threads uninitial
On 2/28/25 20:06, Sudeep Holla wrote:
On Fri, Feb 28, 2025 at 06:51:16PM +0100, Pierre Gondois wrote:
On 2/28/25 14:56, Sudeep Holla wrote:
On Tue, Feb 18, 2025 at 10:10:17PM +0800, Yicong Yang wrote:
From: Yicong Yang
For ACPI we'll build the topology from PPTT and we cannot directly
g
On Fri, Feb 28, 2025 at 06:51:16PM +0100, Pierre Gondois wrote:
>
>
> On 2/28/25 14:56, Sudeep Holla wrote:
> > On Tue, Feb 18, 2025 at 10:10:17PM +0800, Yicong Yang wrote:
> > > From: Yicong Yang
> > >
> > > For ACPI we'll build the topology from PPTT and we cannot directly
> > > get the SMT n
On 2/28/25 14:56, Sudeep Holla wrote:
On Tue, Feb 18, 2025 at 10:10:17PM +0800, Yicong Yang wrote:
From: Yicong Yang
For ACPI we'll build the topology from PPTT and we cannot directly
get the SMT number of each core. Instead using a temporary xarray
to record the heterogeneous information (
On Tue, Feb 18, 2025 at 10:10:17PM +0800, Yicong Yang wrote:
> From: Yicong Yang
>
> For ACPI we'll build the topology from PPTT and we cannot directly
> get the SMT number of each core. Instead using a temporary xarray
> to record the heterogeneous information (from ACPI_PPTT_ACPI_IDENTICAL)
> a
On 18/02/2025 15:10, Yicong Yang wrote:
> From: Yicong Yang
[...]
> @@ -67,6 +108,31 @@ int __init parse_acpi_topology(void)
> cpu_topology[cpu].package_id = topology_id;
> }
>
> + /*
> + * This should be a short loop depending on the number of heterogeneous
On 2025/2/18 22:10, Yicong Yang wrote:
From: Yicong Yang
For ACPI we'll build the topology from PPTT and we cannot directly
get the SMT number of each core. Instead using a temporary xarray
to record the heterogeneous information (from ACPI_PPTT_ACPI_IDENTICAL)
and SMT information of the first
From: Yicong Yang
For ACPI we'll build the topology from PPTT and we cannot directly
get the SMT number of each core. Instead using a temporary xarray
to record the heterogeneous information (from ACPI_PPTT_ACPI_IDENTICAL)
and SMT information of the first core in its heterogeneous CPU cluster
whe
14 matches
Mail list logo
