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 4A605C83005 for ; Fri, 9 Jun 2023 11:17:30 +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=l9vkeFV61JqcSOTwPe+sYAv7KSfv/ffQQC2d/hh53tM=; b=o9uMZNP84r8bmv mXdlIwO48JQ2piqA+x+VuM8FCYGilZrrzQ5nkqTSFs0xhumOx6L82T4VQ9gO5+M/RlJfhtJ/Yg5O6 uzGR+bUeeETDWA0qufAnEa6FbrU5D9WYcfyWNX7Z69wfdf8l1Jfp0Z9sW/hMtSM765I94hRhFpEei DxdcT5K05HHAcS0L8EV6N123qK9NiUJuhorVqs9I1j8m7MswzzoRwUpHsbO5kVtQ3V6ORZBPPA4w1 wjSKRbuyDIDZMkgBqsD0jp5UuwtDB88SRhMhnLBUhoafBXVR1wiWP5S4YkXg8LArFOJ91FHbgYb7i g9PJlmmA8y2SlzCn455w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1q7a7A-00CkJx-2U; Fri, 09 Jun 2023 11:17:08 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1q7a76-00CkGy-39 for linux-arm-kernel@lists.infradead.org; Fri, 09 Jun 2023 11:17:06 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id AC12C6570F; Fri, 9 Jun 2023 11:16:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B7DD5C433D2; Fri, 9 Jun 2023 11:16:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1686309415; bh=4WrX2SLhIZXcNbbPm+X8AVze8JMkGgf+OMnaQdflIDQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=I0ViuyF7DVQYDXJ52IPxtKCSODRiI6e689vhUFyuYXWiiWXsffISPOTGUEyx4An3g YpvlzDyQ70seB/tA0hoSGEEQAK4N0jI45HfT3Dk7DyGtJDkQfFQc1b203n9Yj8Frxf CJ11RVWUSTNHZZXnw/uirFYJYjPcMuCN4ZortSC1rxDo2yuO+3jhWdIPkugCkZsEIb 5opM18frCNcsLs0GfC2aa/bB6Gv7iUiiuOyJ91cyO3i2fUb2OaI03QIhqTIbK6rC6S hzwI3eZp07yoKbtT8LPErqUX8aeLTSTHIRMeWofhYvayVrl3D8ZTQ2UCA57t2WmCjL Ph2LkC+N3P3zg== From: Will Deacon To: Junhao He , linux-kernel@vger.kernel.org, mark.rutland@arm.com, jonathan.cameron@huawei.com Cc: catalin.marinas@arm.com, kernel-team@android.com, Will Deacon , shenyang39@huawei.com, yangyicong@huawei.com, linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, prime.zeng@hisilicon.com, linuxarm@huawei.com Subject: Re: [PATCH] drivers/perf: hisi: Don't migrate perf to the CPU going to teardown Date: Fri, 9 Jun 2023 12:16:45 +0100 Message-Id: <168630624940.3062264.11759068131610200967.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20230608114326.27649-1-hejunhao3@huawei.com> References: <20230608114326.27649-1-hejunhao3@huawei.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230609_041705_057394_3246087B X-CRM114-Status: GOOD ( 11.01 ) 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 Thu, 8 Jun 2023 19:43:26 +0800, Junhao He wrote: > The driver needs to migrate the perf context if the current using CPU going > to teardown. By the time calling the cpuhp::teardown() callback the > cpu_online_mask() hasn't updated yet and still includes the CPU going to > teardown. In current driver's implementation we may migrate the context > to the teardown CPU and leads to the below calltrace: > > ... > [ 368.104662][ T932] task:cpuhp/0 state:D stack: 0 pid: 15 ppid: 2 flags:0x00000008 > [ 368.113699][ T932] Call trace: > [ 368.116834][ T932] __switch_to+0x7c/0xbc > [ 368.120924][ T932] __schedule+0x338/0x6f0 > [ 368.125098][ T932] schedule+0x50/0xe0 > [ 368.128926][ T932] schedule_preempt_disabled+0x18/0x24 > [ 368.134229][ T932] __mutex_lock.constprop.0+0x1d4/0x5dc > [ 368.139617][ T932] __mutex_lock_slowpath+0x1c/0x30 > [ 368.144573][ T932] mutex_lock+0x50/0x60 > [ 368.148579][ T932] perf_pmu_migrate_context+0x84/0x2b0 > [ 368.153884][ T932] hisi_pcie_pmu_offline_cpu+0x90/0xe0 [hisi_pcie_pmu] > [ 368.160579][ T932] cpuhp_invoke_callback+0x2a0/0x650 > [ 368.165707][ T932] cpuhp_thread_fun+0xe4/0x190 > [ 368.170316][ T932] smpboot_thread_fn+0x15c/0x1a0 > [ 368.175099][ T932] kthread+0x108/0x13c > [ 368.179012][ T932] ret_from_fork+0x10/0x18 > ... > > [...] Applied to will (for-next/perf), thanks! [1/1] drivers/perf: hisi: Don't migrate perf to the CPU going to teardown https://git.kernel.org/will/c/7a6a9f1c5a0a 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