Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] irqchip/bcm-6345-l1: fix SMP support
To:     =?UTF-8?Q?=c3=81lvaro_Fern=c3=a1ndez_Rojas?= <noltari@gmail.com>,
        jonas.gorski@gmail.com, Florian Fainelli <f.fainelli@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
References: <20210222201332.30253-1-noltari@gmail.com>
From:   Florian Fainelli <f.fainelli@gmail.com>
Message-ID: <6169cb21-538b-1066-51cb-dd362f811fa1@gmail.com>
Date:   Mon, 22 Feb 2021 13:00:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Firefox/78.0 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <20210222201332.30253-1-noltari@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk


On 2/22/2021 12:13 PM, Álvaro Fernández Rojas wrote:
> Some BCM6358 devices start with Core #1 instead of Core #0.
> Apart from that, SMP is restricted to 1 CPU since BCM6358 has a shared TLB,
> which makes it impossible for the current SMP support to start both CPUs.
> 
> The problem is that smp_processor_id() returns 0 and then cpu_logical_map()
> converts that to 1, which accesses an uninitialized position of intc->cpus[],
> resulting in a kernel panic.

Sounds like you nee to correct the way the cpu_logical_map[] is
populated then?
-- 
Florian