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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 33AB5C433EF for ; Wed, 29 Sep 2021 22:46:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 14F6B61440 for ; Wed, 29 Sep 2021 22:46:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347133AbhI2Wr7 (ORCPT ); Wed, 29 Sep 2021 18:47:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45580 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346734AbhI2Wr5 (ORCPT ); Wed, 29 Sep 2021 18:47:57 -0400 Received: from gandalf.ozlabs.org (gandalf.ozlabs.org [IPv6:2404:9400:2:0:216:3eff:fee2:21ea]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7C033C06161C; Wed, 29 Sep 2021 15:46:15 -0700 (PDT) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4HKWgd3pfqz4xLs; Thu, 30 Sep 2021 08:46:05 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellerman.id.au; s=201909; t=1632955572; bh=mpz+ka0h5K/JeORjuWrldvkBfYvvKVxRrDGCbb8QaxM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=YxATzawCxVN5sXizjsSK6S7RmonpLlF9oJF/MzCwKjaqGOkxQU+wrsp9Aihb7q6f4 8GmMB7JxN87gLBhYVK3Zsr6oocxO4D034AESqrL36bmLJBQR0VbKEMX1PrJ8h9V2He DvukSjI/bK0ghU5kui/5Qg3bKETueRQFs2qi67vi7D8p6Ikua4ZqAn+UP1pJNfYJWc ekBRWmi8RgDX2UCqKpuyvfscHtaX9JBMajmNaoWRV+nv1fRnYpP3UbHtKtmkepjmwr qKNthuRrkZuaeD0FFBoveGtnBDBa4N7MgTnXupxaZSaye1CcxW6kdWE+BJK8lh64qY v6XnWxPI6wDDQ== From: Michael Ellerman To: Ard Biesheuvel Cc: Linux Kernel Mailing List , Keith Packard , Russell King , Catalin Marinas , Will Deacon , Benjamin Herrenschmidt , Christophe Leroy , Paul Mackerras , Paul Walmsley , Palmer Dabbelt , Albert Ou , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Peter Zijlstra , Kees Cook , Andy Lutomirski , Linus Torvalds , Arnd Bergmann , Linux ARM , "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" , linux-riscv , "open list:S390" Subject: Re: [RFC PATCH 4/8] powerpc: add CPU field to struct thread_info In-Reply-To: References: <20210914121036.3975026-1-ardb@kernel.org> <20210914121036.3975026-5-ardb@kernel.org> <87ee99lii7.fsf@mpe.ellerman.id.au> <87pmst1rn9.fsf@mpe.ellerman.id.au> Date: Thu, 30 Sep 2021 08:46:04 +1000 Message-ID: <878rzf0zmb.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ard Biesheuvel writes: > On Tue, 28 Sept 2021 at 02:16, Michael Ellerman wrote: >> >> Michael Ellerman writes: >> > Ard Biesheuvel writes: >> >> On Tue, 14 Sept 2021 at 14:11, Ard Biesheuvel wrote: >> >>> >> >>> The CPU field will be moved back into thread_info even when >> >>> THREAD_INFO_IN_TASK is enabled, so add it back to powerpc's definition >> >>> of struct thread_info. >> >>> >> >>> Signed-off-by: Ard Biesheuvel >> >> >> >> Michael, >> >> >> >> Do you have any objections or issues with this patch or the subsequent >> >> ones cleaning up the task CPU kludge for ppc32? Christophe indicated >> >> that he was happy with it. >> > >> > No objections, it looks good to me, thanks for cleaning up that horror :) >> > >> > It didn't apply cleanly to master so I haven't tested it at all, if you can point me at a >> > git tree with the dependencies I'd be happy to run some tests over it. >> >> Actually I realised I can just drop the last patch. >> >> So that looks fine, passes my standard quick build & boot on qemu tests, >> and builds with/without stack protector enabled. >> > > Thanks. > > Do you have any opinion on how this series should be merged? Kees Cook > is willing to take them via his cross-arch tree, or you could carry > them if you prefer. Taking it via multiple trees at the same time is > going to be tricky, or take two cycles, with I'd prefer to avoid. I don't really mind. If Kees is happy to take it then that's OK by me. If Kees put the series in a topic branch based off rc2 then I could merge that, and avoid any conflicts. cheers