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 X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2430BC10F13 for ; Mon, 8 Apr 2019 16:02:32 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id CFD2020879 for ; Mon, 8 Apr 2019 16:02:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="f07O8cDx" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CFD2020879 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:To :From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=OFDWHndezul89EFU9N+0hdV1FM4NM8Sq3RTXHtZtY9Y=; b=f07O8cDxZVbC3i AAnMWBiArQz+xtr+fcum6oDdFgzkE6aagQpfgzvRyHihQp2ilw/RslxusncH442YfAnnrhGNblRuc LGyXg1Fph7SMZFRe4uRZ0Ax5G6+MIWNWexaQDtxvW/m4RvDvhuLacJmjvVmNW4bxCzoHPb9MUTJlw dADZZyRdInyuQ28INDfQIykMBMIAqrFekZnvi0X2ABj810fvz43tlcBIebVG5HsOZFUnundwGWJX8 xzjavjAxZm5bK/8S1+3vjXMgw5eltUtpPNN7U1Nnr9uNENVI8K4mTlyZoacrAnmlhhKbl3TZ43M7I /BRAad3ML8e+/TtJp4YQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hDWj5-0003Ys-0t; Mon, 08 Apr 2019 16:02:27 +0000 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70] helo=foss.arm.com) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hDWj1-0003XP-Iz for linux-arm-kernel@lists.infradead.org; Mon, 08 Apr 2019 16:02:25 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 1742415AB; Mon, 8 Apr 2019 09:02:23 -0700 (PDT) Received: from filthy-habits.cambridge.arm.com (filthy-habits.cambridge.arm.com [10.1.196.92]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 060353F557; Mon, 8 Apr 2019 09:02:21 -0700 (PDT) From: Marc Zyngier To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/4] arm64: Rework handling of erratum 1188873 Date: Mon, 8 Apr 2019 17:02:12 +0100 Message-Id: <20190408160216.223871-1-marc.zyngier@arm.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190408_090223_625998_B2F79EFE X-CRM114-Status: GOOD ( 11.18 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , Catalin Marinas , Daniel Lezcano , Will Deacon Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org When the handling of erratum 1188873 was merged, it was decided that we'd treat both AArch32 and AArch64 equally by trapping CNTVCT. It turns out that users of such HW feel that the overhead placed on AArch64 userspace is unacceptable, so a less invasive solution had to be investigated. Instead of configuring the trapping once and for all, we switch it on and off on exiting to EL0, depending on whether we have a 32bit task or not. Hopefully the overhead is minimal for non-affected cores. We also take this opportunity to apply the same workaround to Neoverse-N1, which suffers from the same erratum in its early revisions. Marc Zyngier (4): arm64: Restrict ARM64_ERRATUM_1188873 mitigation to AArch32 arm64: Make ARM64_ERRATUM_1188873 depend on COMPAT arm64: Add part number for Neoverse N1 arm64: Apply ARM64_ERRATUM_1188873 to Neoverse-N1 arch/arm64/Kconfig | 12 +++++++----- arch/arm64/include/asm/cputype.h | 2 ++ arch/arm64/kernel/cpu_errata.c | 13 +++++++++++-- arch/arm64/kernel/entry.S | 23 +++++++++++++++++++++++ drivers/clocksource/arm_arch_timer.c | 15 --------------- 5 files changed, 43 insertions(+), 22 deletions(-) -- 2.20.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel