public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: smp-bmips: fix CPU mappings
Date: Wed, 24 Feb 2021 08:07:57 +0100	[thread overview]
Message-ID: <5B471DA5-E911-4B7F-BD9A-CE2901C427FC@gmail.com> (raw)
In-Reply-To: <f4b8718c-ee74-2609-40f6-cb8f62247d51@gmail.com>

Hi Florian,

> El 24 feb 2021, a las 4:45, Florian Fainelli <f.fainelli@gmail.com> escribió:
> 
> 
> 
> On 2/23/2021 4:48 AM, Álvaro Fernández Rojas wrote:
>> When booting bmips with SMP enabled on a BCM6358 running on CPU #1 instead of
>> CPU #0, the current CPU mapping code produces the following:
>> - smp_processor_id(): 0
>> - cpu_logical_map(): 1
>> - cpu_number_map(): 1
>> 
>> This is because SMP isn't supported on BCM6358 since it has a shared TLB, so
>> it is disabled and max_cpus is decreased from 2 to 1.
>> 
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>> ---
>> arch/mips/kernel/smp-bmips.c | 27 +++++++++++++++++----------
>> 1 file changed, 17 insertions(+), 10 deletions(-)
>> 
>> diff --git a/arch/mips/kernel/smp-bmips.c b/arch/mips/kernel/smp-bmips.c
>> index 359b176b665f..c4760cb48a67 100644
>> --- a/arch/mips/kernel/smp-bmips.c
>> +++ b/arch/mips/kernel/smp-bmips.c
>> @@ -134,17 +134,24 @@ static void __init bmips_smp_setup(void)
>> 	if (!board_ebase_setup)
>> 		board_ebase_setup = &bmips_ebase_setup;
>> 
>> -	__cpu_number_map[boot_cpu] = 0;
>> -	__cpu_logical_map[0] = boot_cpu;
>> -
>> -	for (i = 0; i < max_cpus; i++) {
>> -		if (i != boot_cpu) {
>> -			__cpu_number_map[i] = cpu;
>> -			__cpu_logical_map[cpu] = i;
>> -			cpu++;
>> +	if (max_cpus > 1) {
>> +		__cpu_number_map[boot_cpu] = 0;
>> +		__cpu_logical_map[0] = boot_cpu;
>> +
>> +		for (i = 0; i < max_cpus; i++) {
>> +			if (i != boot_cpu) {
>> +				__cpu_number_map[i] = cpu;
>> +				__cpu_logical_map[cpu] = i;
>> +				cpu++;
>> +			}
>> +			set_cpu_possible(i, 1);
>> +			set_cpu_present(i, 1);
>> 		}
>> -		set_cpu_possible(i, 1);
>> -		set_cpu_present(i, 1);
>> +	} else {
>> +		__cpu_number_map[0] = boot_cpu;
>> +		__cpu_logical_map[0] = 0;
>> +		set_cpu_possible(0, 1);
>> +		set_cpu_possible(0, 1);
> 
> Duplicate line, with that fixed:

Nice catch, it should be set_cpu_present().

> 
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> -- 
> Florian


  reply	other threads:[~2021-02-24  7:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 12:48 [PATCH] mips: smp-bmips: fix CPU mappings Álvaro Fernández Rojas
2021-02-24  3:45 ` Florian Fainelli
2021-02-24  7:07   ` Álvaro Fernández Rojas [this message]
2021-02-24  7:33 ` [PATCH v2] " Álvaro Fernández Rojas
2021-02-27  6:47   ` Álvaro Fernández Rojas
2021-03-01 12:33     ` Thomas Bogendoerfer
2021-03-01 14:50   ` Thomas Bogendoerfer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B471DA5-E911-4B7F-BD9A-CE2901C427FC@gmail.com \
    --to=noltari@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox