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 7AA33C4332F for ; Wed, 13 Dec 2023 17:26:02 +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:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=3tmFi7h+3nrpoNdzi8S3iUPP7OzMm1PfiYVSDtAm+Js=; b=Fn3MnVYx3oOz7B xg5uQsdPqFivp8uUpogwiP/s7DcIC7xvzjg9CCotAee2fZ9Ywb3mDG3MjIQTBHwbzPpU6JtEjhtNc DoN35CPr6mPZguBTNThBGXDA/UkNxRH8YSvhwpAD4iiZE9savPFFaeJJ1nzjVunBQXLNUNUn3Cc29 2eoBhvDYZDfZwQcozOEsxSNYrZiv12yavC4bFJbO6PBka/ah/VOxvqsKBBBtHmb6N+IqBOrCaxzci MxgmWr15cLbddJbmmbL0uitQ7sYLHGQHjettFFwXaHX8TY/qd1e3C2e6UpqUATrtQsIQoGUpc3xjW Akj3T0NVMK/mycEI8VVw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rDSzH-00FanR-0C; Wed, 13 Dec 2023 17:25:35 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rDSzD-00Falc-1q for linux-arm-kernel@lists.infradead.org; Wed, 13 Dec 2023 17:25:33 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id DCE5161EA6; Wed, 13 Dec 2023 17:25:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 68E76C433CB; Wed, 13 Dec 2023 17:25:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1702488327; bh=os/O9QRbd6GtssmBxSCNBepFlJx3aTs+48FG9mog+JI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=uptNqPYqQBgLrlruDI8pKNwnTAj3gnd9APZCnXU5FsxS3ca1+p6sKPVCDs5pibKUj gf2zhPeFJuWT6Yy0KghZ97jMdEfJSW9NOTLv0mAKG6dyRZt5VBQPr8C1IwwiMIE/vQ p48VcB5xEpvords8Ox1Vbo/bLCAc2pUTVR2u2FYSjjieE0mZWokSj6COQqk+VplWw2 hkonE1YOXNEXKZJIO0WTpQmr3WpL4jK/6zsWCoMpkPpeUUHsaVTTLUryEz//C17aSX UWErmHlEIe1p6snJPI/uQ2kmgQD7ywQXcX/ICduLMxI62ROZqNN4R0iALgEOQnYdIu Os+MS2Z9UnR8w== From: Will Deacon To: Mark Rutland , linux-arm-kernel@lists.infradead.org Cc: catalin.marinas@arm.com, kernel-team@android.com, Will Deacon , ardb@kernel.org Subject: Re: [PATCH 0/2] arm64: cpucap handling cleanups Date: Wed, 13 Dec 2023 17:25:18 +0000 Message-Id: <170248332281.2991306.7731192579703060918.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20231212170910.3745497-1-mark.rutland@arm.com> References: <20231212170910.3745497-1-mark.rutland@arm.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231213_092531_654115_24C5AA92 X-CRM114-Status: UNSURE ( 9.95 ) X-CRM114-Notice: Please train this message. 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 On Tue, 12 Dec 2023 17:09:08 +0000, Mark Rutland wrote: > The recent changes to remove cpus_have_const_cap() left a period between > detecting cpucaps and patching alternatives where it is necessary to use > cpus_have_cap() to check that a cpucap has been detected. During this > period we do a few things, and there's a risk that code using a mixture > of cpus_have_cap() and alternative_has_cap_*() sees an inconsistent > state. > > [...] Applied to arm64 (for-next/cpufeature), thanks! Basing the series on for-next/fixes makes it fiddly to manage, so I dropped the kpti_install_ng_mappings() hunk from patch 1 and will re-introduce it when I merge the branches together. [1/2] arm64: Cleanup system cpucap handling https://git.kernel.org/arm64/c/63a2d92e1461 [2/2] arm64: Align boot cpucap handling with system cpucap handling https://git.kernel.org/arm64/c/eb15d707c252 Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel