From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from elvis.franken.de (elvis.franken.de [193.175.24.41]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 4DF5916D4F4; Fri, 21 Jun 2024 08:22:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.175.24.41 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718958143; cv=none; b=sUSi2zXhztXWYYsfEJhN3zIYa2LHTq0cM+tEsOLNrddRRtMsmhr28dwXSSgGGTa4OY+G1+Vd0sXPWsYjs89ZO1vNJvLLiNJ7LdSHC69scFGO3kZPk6q66aWa+2vkoUn6FsrJcFfYYgeDBI/UoWXcwVAoQ9ZgT3oxOpjDDMqOQIw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718958143; c=relaxed/simple; bh=dgT8q2RUD4AsRrCrgspBvokTXMmqeYQLjIWJc/q4mjM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ZFDfmdP5ufbVCFcTVwxhk7RyUp/qO+V/6PANDyvNmT7H2zftfGK79Sky5XAhHZ9tlrNgb39CZxqTQajvNUdSQX9UvY3IsMbdt6HfyPTx/R6DVA8QP1bY0hOolO7QcnE2EwNbMu8u1aKznHoHfgBgj4j7o/TSVaT3FTGgOeIKGEo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=alpha.franken.de; spf=pass smtp.mailfrom=alpha.franken.de; arc=none smtp.client-ip=193.175.24.41 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=alpha.franken.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=alpha.franken.de Received: from uucp by elvis.franken.de with local-rmail (Exim 3.36 #1) id 1sKZWX-0001Oj-00; Fri, 21 Jun 2024 10:21:33 +0200 Received: by alpha.franken.de (Postfix, from userid 1000) id 88B31C0120; Fri, 21 Jun 2024 10:21:17 +0200 (CEST) Date: Fri, 21 Jun 2024 10:21:17 +0200 From: Thomas Bogendoerfer To: Jiaxun Yang Cc: Aleksandar Rikalo , Aleksandar Rikalo , Chao-ying Fu , Daniel Lezcano , Geert Uytterhoeven , Greg Ungerer , Hauke Mehrtens , Ilya Lipnitskiy , linux-kernel@vger.kernel.org, "linux-mips@vger.kernel.org" , Marc Zyngier , "paulburton@kernel.org" , Peter Zijlstra , Serge Semin , Thomas Gleixner , Tiezhu Yang Subject: Re: [PATCH v4 00/14] MIPS: Support I6500 multi-cluster configuration Message-ID: References: <20240511104341.151550-1-aleksandar.rikalo@syrmia.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Fri, Jun 21, 2024 at 12:05:32AM +0100, Jiaxun Yang wrote: > > > 在2024年6月20日六月 下午6:56，Thomas Bogendoerfer写道： > > On Sat, May 11, 2024 at 12:43:27PM +0200, Aleksandar Rikalo wrote: > >> Taken from Paul Burton MIPS repo with minor changes from Chao-ying Fu. > >> Tested with 64r6el_defconfig on Boston board in 2 cluster/2 VPU and > >> 1 cluster/4 VPU configurations. > > > > which existing CPUs can use this ? > > Besides Boston are some multi cluster I6500 systems in wild, including Fungible F1, > which comes with 52 cores in data panel. > > Those vendors show no interest on mainline kernel support though. ok, so looking at the series it touches areas with different maintainers, I'm fine taking the MIPS parts, can I simply cherry-pick them out of the series ? Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]