From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AF462C7EE23 for ; Fri, 24 Feb 2023 19:01:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=m+Y3B3sbWtOmXPIV0rT9lKfPp6BIoDMVyFKJZGfPCB0=; b=ZoBbrNkCnwRE/d WHs8Pe3bI9q+2bX1AvVuJFtHwyujMZRjs7+EFqzrp2HqCWCda+CL08A5du1NTTVmJlfJi5BrY2ZvR K0xLBWc2xj9WYF/wFgtLrdKn9ObQ3yNGqIl6rZvcG2fy+fsk+JH6lYtqxcKPJOnKT60x8r6BDLv6G vPdYKpKVz4EW4UKF4ccWBoFSyZPHSaBku8liqKFTOA+G7FJlgclaqJ1XKDqvu3SkhpngHSbaXWGvC b3amcSziHx8bIe3+0Bc9wwVg5RnRA1IJkUz27JsprBWakQY5MAkxvqhsuDaOiRoaOTkfXKgWSQ6I8 mad2206/G2Gq65S8FTAQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pVdJ3-003Zxb-N9; Fri, 24 Feb 2023 19:00:33 +0000 Received: from out-2.mta0.migadu.com ([2001:41d0:1004:224b::2]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pVdJ0-003ZwA-QN for linux-arm-kernel@lists.infradead.org; Fri, 24 Feb 2023 19:00:32 +0000 Date: Fri, 24 Feb 2023 19:00:19 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1677265226; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=oaZbAma9q5k2YnUb1EqWLr5/cSyjvUsdGUP9cWAw62w=; b=XPXsLdg+En+CeVHrL7434uTU8wCgGNasz7brMbnvCR/XNGq1HeXx9AiT3MnNho1qCRWfHW DhfC7i4VJTWCHlbgR5OzX48x68QKRmjJFgDUivubGOgzGvkCCmMJAmptRgxrY404eB1Srk /EK9Zc3bzHpjZ4k2nP2Zyypaes3Q5R4= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Oliver Upton To: James Morse Cc: linux-arm-kernel@lists.infradead.org, Catalin Marinas , Will Deacon , Mark Rutland , Lorenzo Pieralisi , Sudeep Holla , Marc Zyngier Subject: Re: [RFC PATCH 0/3] arm64: errata: Disable FWB on parts with non-ARM interconnects Message-ID: References: <20230216182201.1705406-1-james.morse@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230224_110031_269994_EE0CBC4D X-CRM114-Status: GOOD ( 17.99 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org James, I realize I didn't send my reply earlier this week and came back to this when looking for your reply on another thread. Sorry about that. On Tue, Feb 21, 2023 at 05:41:35PM +0000, James Morse wrote: [...] > > Wait, what? Is there a legitimate concern that affected systems are in > > the wild today, or is there enough time for affected platforms to go and > > implement the necessary firmware interface? > > The one platform that arm is aware of isn't shipping yet - I assume it will implement the > firmware interface. > > But I don't think arm always know what it is people are building ... it certainly doesn't > reach me. This affects a whole host of CPUs, I wouldn't be surprised if there is an > existing part out there that is affected. I was only thinking of the V2 system that is unobtainable at this point. Actually looking at the laundry list of affected cores it does make more sense that this problem already exists today. > > I'm rather troubled by the idea of enabling this by default on systems > > that use these cores unless there really is no opportunity to > > course-correct. > > It's the choice between correctness and performance. Probability says unless the CPU is > Neoverse-V2 (which is that one platform), you're not affected. But how much does > correctness matter? I'd hate to have to debug "1 in a 100 times the guest doesn't boot". Oh, not looking to make that tradeoff with my line of questioning :) I was more curious if there was still an opportunity for affected systems to explicitly opt-in to the mitigation. Seems that the answer is "no", sadly. -- Thanks, Oliver _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel