From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f53.google.com (mail-pj1-f53.google.com [209.85.216.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E5BBAED3 for ; Tue, 20 Sep 2022 02:49:26 +0000 (UTC) Received: by mail-pj1-f53.google.com with SMTP id i15-20020a17090a4b8f00b0020073b4ac27so1072084pjh.3 for ; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=lnIljFKp1ED3j5wPYTN7mdVUfk7FiKkjAkcUsYSYUMCZpdQ5U8vkDdIo4K0hiw1RH3 +GFslTzjK43l0+rnV0YItKzr73eqf7dBzWl3BzQNkwS39xy9TTbRZE0df01R7//5oEJr gCiIxE6Vh5vvSGpkucOrRiDvI3G32scMCweV8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=y06pPRIgCDHoMzbbBcnO6B0Dv8OV4jW17eQkDKyIXX1dYRXtk2CgMchiox+dY02R34 Umq1ha3AIzMHW87EQTygQDqkGvbXqCB+6ScLZbhurqsziWJnxh3DGsg7Q/pRS3NKcILV Tjrgyg3I1UT1+mM7RMMzmqQ2DvWFz0v0EnWC+1ommbfIMzlkE0PnehRVl14s2v41YbxI 2IzurcmuQOc/JwZw5wqVRFiweRi198Y2nfRIzBpxQbsHWgdK3hriBqsF/niqWlWCIT+N 1we4AlTgpCebQNKwkqtMKC408n+TC9eedzBthkJf3PEZPP/79bvOyNVeLZTHVMZDlSM7 Th+w== X-Gm-Message-State: ACrzQf0LLnUBWRHz64ZbKB0U42uOmjfhJRASpGccWkNUV0UK//1Yd0dg nYym1rV1NSnJMQz2gpl75wJpqg== X-Google-Smtp-Source: AMsMyM7S+Aze7xjQjfeMxV1IycjxiN9uStAZCOz26LYAWGHUeF519ICUTt9w2zkpb7un7hJ/v+di5Q== X-Received: by 2002:a17:902:8e84:b0:178:57e4:805b with SMTP id bg4-20020a1709028e8400b0017857e4805bmr2741327plb.144.1663642166279; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) Received: from google.com ([240f:75:7537:3187:5744:3726:1f8b:92ad]) by smtp.gmail.com with ESMTPSA id j6-20020a170903024600b00178a9b193cfsm119779plh.140.2022.09.19.19.49.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Sep 2022 19:49:25 -0700 (PDT) Date: Tue, 20 Sep 2022 11:49:14 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Cc: linux@armlinux.org.uk, linux-imx@nxp.com, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, rostedt@goodmis.org, pmladek@suse.com, senozhatsky@chromium.org, john.ogness@linutronix.de, Andrew Morton , linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-omap@vger.kernel.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, loongarch@lists.linux.dev, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, linux-perf-users@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-xtensa@linux-xtensa.org, linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arch@vger.kernel.org, kasan-dev@googlegroups.com Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Message-ID: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> Precedence: bulk X-Mailing-List: loongarch@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220919101522.021681292@infradead.org> On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky 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.librecores.org (lists.librecores.org [88.198.125.70]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A347C54EE9 for ; Tue, 20 Sep 2022 02:49:30 +0000 (UTC) Received: from [172.31.1.100] (localhost.localdomain [127.0.0.1]) by mail.librecores.org (Postfix) with ESMTP id C9918249BB; Tue, 20 Sep 2022 04:49:29 +0200 (CEST) Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) by mail.librecores.org (Postfix) with ESMTPS id E019A2496F for ; Tue, 20 Sep 2022 04:49:27 +0200 (CEST) Received: by mail-pj1-f51.google.com with SMTP id d64-20020a17090a6f4600b00202ce056566so9346468pjk.4 for ; Mon, 19 Sep 2022 19:49:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=lnIljFKp1ED3j5wPYTN7mdVUfk7FiKkjAkcUsYSYUMCZpdQ5U8vkDdIo4K0hiw1RH3 +GFslTzjK43l0+rnV0YItKzr73eqf7dBzWl3BzQNkwS39xy9TTbRZE0df01R7//5oEJr gCiIxE6Vh5vvSGpkucOrRiDvI3G32scMCweV8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=2/Ix06k7gdyuTGqX585HuSZxE0N1EEf449AwUBWfWU59flG3SmPnUQ+XZp+rU78Xw3 sHlftQxE/R8q2S/i7MRflCfuqcIFvDQUx+LtF251bV0ljv/K8CtC2Woi6RKEKLOMPcFu HQK11zKOro64WCP0agQqJBYgXA2ukI7denlvSxRBgQBcdrkeVtCP5K/VSXW+uGly59Yp i0qr3DoxKP1lELxIt/8r/y2Ap747M2r92j3yJfn5rDMZT4I2sUuNmyZbRrYWj0t/zg9g /iZPu92/eIAUJJ/dqjkUsdRnSsWad/8mOBONIifg0NLugQbersE9eCIgF+Zz6E4BqPnn IISQ== X-Gm-Message-State: ACrzQf1i73/MDoOy6bg1GUnLi6qdSc+3OCIMXRohl6hGN+tw/PFspk9r RWaJHEdtoFNv3p7PuE//ebQN3w== X-Google-Smtp-Source: AMsMyM7S+Aze7xjQjfeMxV1IycjxiN9uStAZCOz26LYAWGHUeF519ICUTt9w2zkpb7un7hJ/v+di5Q== X-Received: by 2002:a17:902:8e84:b0:178:57e4:805b with SMTP id bg4-20020a1709028e8400b0017857e4805bmr2741327plb.144.1663642166279; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) Received: from google.com ([240f:75:7537:3187:5744:3726:1f8b:92ad]) by smtp.gmail.com with ESMTPSA id j6-20020a170903024600b00178a9b193cfsm119779plh.140.2022.09.19.19.49.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Sep 2022 19:49:25 -0700 (PDT) Date: Tue, 20 Sep 2022 11:49:14 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Message-ID: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220919101522.021681292@infradead.org> X-BeenThere: openrisc@lists.librecores.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion around the OpenRISC processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, linux-mips@vger.kernel.org, kasan-dev@googlegroups.com, sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org, linux-clk@vger.kernel.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-hexagon@vger.kernel.org, x86@kernel.org, linux@armlinux.org.uk, linux-csky@vger.kernel.org, linux-acpi@vger.kernel.org, mingo@redhat.com, linux-imx@nxp.com, linux-snps-arc@lists.infradead.org, virtualization@lists.linux-foundation.org, pmladek@suse.com, john.ogness@linutronix.de, linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-um@lists.infradead.org, rostedt@goodmis.org, linux-m68k@lists.linux-m68k.org, openrisc@lists.librecores.org, loongarch@lists.linux.dev, linux-tegra@vger.kernel.org, tglx@linutronix.de, linux-omap@vger.kernel.org, linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, senozhatsky@chromium.org, linux-alpha@vger.kernel.org, Andrew Morton , linuxppc-dev@lists.ozlabs.org Errors-To: openrisc-bounces@lists.librecores.org Sender: "OpenRISC" On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Date: Tue, 20 Sep 2022 02:49:14 +0000 Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Message-Id: List-Id: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> In-Reply-To: <20220919101522.021681292@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Peter Zijlstra Cc: linux@armlinux.org.uk, linux-imx@nxp.com, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, rostedt@goodmis.org, pmladek@suse.com, senozhatsky@chromium.org, john.ogness@linutronix.de, Andrew Morton , linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-omap@vger.kernel.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, loongarch@lists.linux.dev, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, linux-perf-users@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-xtensa@linux-xtensa.org, linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arch@vger.kernel.org, kasan-dev@googlegroups.com On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Date: Tue, 20 Sep 2022 11:49:14 +0900 Message-ID: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=lnIljFKp1ED3j5wPYTN7mdVUfk7FiKkjAkcUsYSYUMCZpdQ5U8vkDdIo4K0hiw1RH3 +GFslTzjK43l0+rnV0YItKzr73eqf7dBzWl3BzQNkwS39xy9TTbRZE0df01R7//5oEJr gCiIxE6Vh5vvSGpkucOrRiDvI3G32scMCweV8= Content-Disposition: inline In-Reply-To: <20220919101522.021681292@infradead.org> List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Peter Zijlstra Cc: linux@armlinux.org.uk, linux-imx@nxp.com, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, rostedt@goodmis.org, pmladek@suse.com, senozhatsky@chromium.org, john.ogness@linutronix.de, Andrew Morton , linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-omap@vger.kernel.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, loongarch@lists.linux.dev, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, linux-perf-users@v On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky 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 7693CC6FA90 for ; Tue, 20 Sep 2022 02:49:44 +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=zPIwXMv6zjDc9ngaXBS08s4n0TRA5msowC55C7XW7LE=; b=F12Imd+ysMgtRg c9ZbTARVgeQEmMmvAGTV2eXNDkvea7G5aryMZXtx390VigzjWIAyTYAkBNJLHVWTIRro6NffsIVr4 KKXZXMgsgg8Ml/ebQkeDLfw+r7+bFSIsfv5HkyLPChEYJG3xKoHF760CYxyjEuryjOihluYGiot9j weaRhBVmcfU2pIfPpPdvEY5H7CDJBkoGFnY1wgZXDDxqwQOHK2B1NAmUXpGno6ibls21w+Q7tBQCz 2PVoBhLzvVpzeTw8uzLWRcMjuuOJSfuM99iogruKVK6UnX3xnRy8JQ7xT0cADbx4qW0MCwDlihhTO b8KOTHDzgNYUuLWiCkcw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oaTKG-00HNAL-6M; Tue, 20 Sep 2022 02:49:32 +0000 Received: from mail-pl1-x62d.google.com ([2607:f8b0:4864:20::62d]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oaTKD-00HN8Q-VU for linux-riscv@lists.infradead.org; Tue, 20 Sep 2022 02:49:31 +0000 Received: by mail-pl1-x62d.google.com with SMTP id w10so159890pll.11 for ; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=lnIljFKp1ED3j5wPYTN7mdVUfk7FiKkjAkcUsYSYUMCZpdQ5U8vkDdIo4K0hiw1RH3 +GFslTzjK43l0+rnV0YItKzr73eqf7dBzWl3BzQNkwS39xy9TTbRZE0df01R7//5oEJr gCiIxE6Vh5vvSGpkucOrRiDvI3G32scMCweV8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=KVwE1pyjDimLp5gruNqwChpEH5GMZdzjR5a2AbOMQHIt+37E83XEmsFZiDyD1/JRwa H7IehLiGLORWOfNouMp+b/lVZszGQWsy90ZPdKbeu6kacYWgxu74BmZGfdukxaloaoe1 b6kz56MIMh22bmDRGq1MV7ol9jyLp9ZcD1S6ca37R3pnPRlQrMlyYbDVZ/9yU/DJ9jIY bz1qfBPQ7c50s5Va+bF/SlZzsendo3hqm5qMClu1awit20JfghN2e3MSUJOqFnjRngbd EO2oLTnsTSg+7yIPSFZjovzz8PYiZG+SirJQu1jUld/f+jA8Kwf+pxF/X9d2+b+T7Ptm K0DA== X-Gm-Message-State: ACrzQf2m2Q3RDa8zRsHgCCm0OzBAvYDzZkJW9z1ARF77s4PnslHIQ9hn DAWHDKOs1mA4sD6oJKwW/hZpPQ== X-Google-Smtp-Source: AMsMyM7S+Aze7xjQjfeMxV1IycjxiN9uStAZCOz26LYAWGHUeF519ICUTt9w2zkpb7un7hJ/v+di5Q== X-Received: by 2002:a17:902:8e84:b0:178:57e4:805b with SMTP id bg4-20020a1709028e8400b0017857e4805bmr2741327plb.144.1663642166279; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) Received: from google.com ([240f:75:7537:3187:5744:3726:1f8b:92ad]) by smtp.gmail.com with ESMTPSA id j6-20020a170903024600b00178a9b193cfsm119779plh.140.2022.09.19.19.49.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Sep 2022 19:49:25 -0700 (PDT) Date: Tue, 20 Sep 2022 11:49:14 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Cc: linux@armlinux.org.uk, linux-imx@nxp.com, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, rostedt@goodmis.org, pmladek@suse.com, senozhatsky@chromium.org, john.ogness@linutronix.de, Andrew Morton , linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-omap@vger.kernel.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, loongarch@lists.linux.dev, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, linux-perf-users@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-xtensa@linux-xtensa.org, linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arch@vger.kernel.org, kasan-dev@googlegroups.com Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Message-ID: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220919101522.021681292@infradead.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220919_194930_054021_FE90F7C3 X-CRM114-Status: UNSURE ( 8.86 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-riscv@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-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv 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 9380BC6FA91 for ; Tue, 20 Sep 2022 02:49:36 +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=2rXnGd+ldke6Hz7084nQsl25TxKs9+kBEyWZUkG2cUk=; b=tJEe7LV9AWvzRM mE04X6PbJLVlVw4Vvmc8hxEG/vF7mDWQSkWkhoCbrhtUBFt4Htec1SkP8RqkqM84GV67k+uJw5ncK 4swHkQYacbw5SaGR1f5wCZIkxOHvVZBcL7CZM3HCjF7HH1n2rRw6aEb1zenSiZJM4avfZjMeCdr5x 0XRn5ZqEeTKpQIyRww/XdwlZgsGCDmjUz4wtwwTQSoKlO+yry6DVrEpfDp4RtXkEIy0JEqcHQxGtY hgKOFf5ZaUI8YvTr7hmeotfGdICkK21zjTUYN+r+HLsMff+PdhY2qsv5prdjv33T+F+fQWPep09hW kV1Y1lfUuNzS+TX84rNw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oaTKH-00HNBJ-Ik; Tue, 20 Sep 2022 02:49:33 +0000 Received: from mail-pl1-x62d.google.com ([2607:f8b0:4864:20::62d]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oaTKD-00HN8R-Uj for linux-snps-arc@lists.infradead.org; Tue, 20 Sep 2022 02:49:31 +0000 Received: by mail-pl1-x62d.google.com with SMTP id w13so1060227plp.1 for ; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=lnIljFKp1ED3j5wPYTN7mdVUfk7FiKkjAkcUsYSYUMCZpdQ5U8vkDdIo4K0hiw1RH3 +GFslTzjK43l0+rnV0YItKzr73eqf7dBzWl3BzQNkwS39xy9TTbRZE0df01R7//5oEJr gCiIxE6Vh5vvSGpkucOrRiDvI3G32scMCweV8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=JsiIPUKqmcdOKOmRdS6TToR3GHRKLURJY9fHmfoq6BbAAuRNZxoqZLfJo+UYg0KLJY 8Sz81oIe3NUIDJ9Y7OGM7qRXroU+3fDTLE+s7L3giWBNNlQBsKbbJBeu5McaOdhHv+YY rkIR05EXmKqDPVUolW1EED1my+yOCa81MqdDl5T81w0tVlKIGXxHpYBywh87y8pkvG3V A8wWSV10j8nS2nTOlv2cO60oWmfNkMaCXH/xLHk770kBLn1l2RAhprISQ2ld0zJ9FeCG JZFsVQd+Zdo1pH4pcr60VJr3ZJJk2xREU8jMNFcAsd6MWyYXq2xkrTJZ+pRIRrh6W0TU BWKg== X-Gm-Message-State: ACrzQf03oQtTh8pyhNsPr31elvk2hnhCCaa7WV0pAkE/tvpULm9yHmnj qjNzdt8tspvxH1f5KCrSUtmG+w== X-Google-Smtp-Source: AMsMyM7S+Aze7xjQjfeMxV1IycjxiN9uStAZCOz26LYAWGHUeF519ICUTt9w2zkpb7un7hJ/v+di5Q== X-Received: by 2002:a17:902:8e84:b0:178:57e4:805b with SMTP id bg4-20020a1709028e8400b0017857e4805bmr2741327plb.144.1663642166279; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) Received: from google.com ([240f:75:7537:3187:5744:3726:1f8b:92ad]) by smtp.gmail.com with ESMTPSA id j6-20020a170903024600b00178a9b193cfsm119779plh.140.2022.09.19.19.49.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Sep 2022 19:49:25 -0700 (PDT) Date: Tue, 20 Sep 2022 11:49:14 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Cc: linux@armlinux.org.uk, linux-imx@nxp.com, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, rostedt@goodmis.org, pmladek@suse.com, senozhatsky@chromium.org, john.ogness@linutronix.de, Andrew Morton , linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-omap@vger.kernel.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, loongarch@lists.linux.dev, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, linux-perf-users@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-xtensa@linux-xtensa.org, linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arch@vger.kernel.org, kasan-dev@googlegroups.com Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Message-ID: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220919101522.021681292@infradead.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220919_194930_054614_B14C4090 X-CRM114-Status: UNSURE ( 8.86 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-snps-arc@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux on Synopsys ARC Processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-snps-arc" Errors-To: linux-snps-arc-bounces+linux-snps-arc=archiver.kernel.org@lists.infradead.org On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky _______________________________________________ linux-snps-arc mailing list linux-snps-arc@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-snps-arc 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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (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 30FA3C54EE9 for ; Tue, 20 Sep 2022 02:50:10 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4MWmHN2mbhz3c1c for ; Tue, 20 Sep 2022 12:50:08 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=chromium.org header.i=@chromium.org header.a=rsa-sha256 header.s=google header.b=lnIljFKp; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=chromium.org (client-ip=2607:f8b0:4864:20::1031; helo=mail-pj1-x1031.google.com; envelope-from=senozhatsky@chromium.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=chromium.org header.i=@chromium.org header.a=rsa-sha256 header.s=google header.b=lnIljFKp; dkim-atps=neutral Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4MWmGg0LMcz2ypD for ; Tue, 20 Sep 2022 12:49:28 +1000 (AEST) Received: by mail-pj1-x1031.google.com with SMTP id o70-20020a17090a0a4c00b00202f898fa86so1095124pjo.2 for ; Mon, 19 Sep 2022 19:49:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=lnIljFKp1ED3j5wPYTN7mdVUfk7FiKkjAkcUsYSYUMCZpdQ5U8vkDdIo4K0hiw1RH3 +GFslTzjK43l0+rnV0YItKzr73eqf7dBzWl3BzQNkwS39xy9TTbRZE0df01R7//5oEJr gCiIxE6Vh5vvSGpkucOrRiDvI3G32scMCweV8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=rI0IpfDVb05suW6mssP/QFC86Iigix9NLenW3JQ6Phs=; b=x6krF5hGBCpCQ2tRLNHFMlrZOJaX0aLZQpMEboHJnZw2mR4HS1grq+nAFkgs3PeaG6 y6bekcjhlqTJK6M/T/hlGfG4iT2XOkbTOdd2b5eT+kUUnhw4+VsFRAC000S68V3TpRE6 vy0+ABm5S+lIZw3KxmONuHl4Fv+hGjhb6XDJwaB3bDYy3ic6Jvjy3ie1kqQEzO4famNE fA0zRC9KYQPdvsRMcchhVjItNYRSpjO4HKolQMnr3xlyj7H2AkrWveSK9L+L1ZSSKHmg 8j9YH1jMMjiQkVEHyF01I3lS5y/YngQBh2EgFVnW66l0jUXbpEUstNUfHyVC/5kWreI5 KFzQ== X-Gm-Message-State: ACrzQf2HTfg/WZ9rqa7th80W1+7sd1QIB74g8u7/5JMjNwsmkOcN0k4o 0+8iq6NcVXvOhVkF7Z8uc0wQRw== X-Google-Smtp-Source: AMsMyM7S+Aze7xjQjfeMxV1IycjxiN9uStAZCOz26LYAWGHUeF519ICUTt9w2zkpb7un7hJ/v+di5Q== X-Received: by 2002:a17:902:8e84:b0:178:57e4:805b with SMTP id bg4-20020a1709028e8400b0017857e4805bmr2741327plb.144.1663642166279; Mon, 19 Sep 2022 19:49:26 -0700 (PDT) Received: from google.com ([240f:75:7537:3187:5744:3726:1f8b:92ad]) by smtp.gmail.com with ESMTPSA id j6-20020a170903024600b00178a9b193cfsm119779plh.140.2022.09.19.19.49.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Sep 2022 19:49:25 -0700 (PDT) Date: Tue, 20 Sep 2022 11:49:14 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Subject: Re: [PATCH v2 25/44] printk: Remove trace_.*_rcuidle() usage Message-ID: References: <20220919095939.761690562@infradead.org> <20220919101522.021681292@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220919101522.021681292@infradead.org> X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, linux-mips@vger.kernel.org, kasan-dev@googlegroups.com, sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org, linux-clk@vger.kernel.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-hexagon@vger.kernel.org, x86@kernel.org, linux@armlinux.org.uk, linux-csky@vger.kernel.org, linux-acpi@vger.kernel.org, mingo@redhat.com, linux-imx@nxp.com, linux-snps-arc@lists.infradead.org, virtualization@lists.linux-foundation.org, pmladek@suse.com, john.ogness@linutronix.de, linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-um@lists.infradead.org, rostedt@goodmis.org, linux-m68k@lists.linux-m68k.org, openrisc@lists.librecores.org, loongarch@lists.linux.dev, linux-tegra@vger.kernel.org, tglx@linutronix.de, linux-omap@vger.kernel.org, linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, senozhatsky@chromium.org, linux-alpha@vger.kernel.or g, Andrew Morton , linuxppc-dev@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On (22/09/19 12:00), Peter Zijlstra wrote: > The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console > tracepoint"), was printk usage from the cpuidle path where RCU was > already disabled. > > Per the patches earlier in this series, this is no longer the case. > > Signed-off-by: Peter Zijlstra (Intel) > Reviewed-by: Sergey Senozhatsky > Acked-by: Petr Mladek Acked-by: Sergey Senozhatsky