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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4DADC6FD1D for ; Fri, 17 Mar 2023 16:02:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230063AbjCQQCR (ORCPT ); Fri, 17 Mar 2023 12:02:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57728 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229879AbjCQQCP (ORCPT ); Fri, 17 Mar 2023 12:02:15 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6530DE4C48 for ; Fri, 17 Mar 2023 09:02:14 -0700 (PDT) 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 ams.source.kernel.org (Postfix) with ESMTPS id 207EDB8262D for ; Fri, 17 Mar 2023 16:02:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6C151C433EF; Fri, 17 Mar 2023 16:02:09 +0000 (UTC) Date: Fri, 17 Mar 2023 16:02:06 +0000 From: Catalin Marinas To: Kristina Martsenko Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, Will Deacon , Marc Zyngier , Oliver Upton , James Morse , Suzuki K Poulose , Zenghui Yu , Mark Rutland , Mark Brown , Luis Machado , Vladimir Murzin , linux-kernel@vger.kernel.org Subject: Re: [PATCH 08/10] arm64: mops: handle single stepping after MOPS exception Message-ID: References: <20230216160012.272345-1-kristina.martsenko@arm.com> <20230216160012.272345-9-kristina.martsenko@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230216160012.272345-9-kristina.martsenko@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 16, 2023 at 04:00:10PM +0000, Kristina Martsenko wrote: > When a MOPS main or epilogue instruction is being executed, the task may > get scheduled on a different CPU and restart execution from the prologue > instruction. If the main or epilogue instruction is being single stepped > then it makes sense to finish the step and take the step exception > before starting to execute the next (prologue) instruction. So > fast-forward the single step state machine when taking a MOPS exception. > > This means that if a main or epilogue instruction is single stepped with > ptrace, the debugger will sometimes observe the PC moving back to the > prologue instruction. (As already mentioned, this should be rare as it > only happens when the task is scheduled to another CPU during the step.) > > This also ensures that perf breakpoints count prologue instructions > consistently (i.e. every time they are executed), rather than skipping > them when there also happens to be a breakpoint on a main or epilogue > instruction. > > Signed-off-by: Kristina Martsenko Acked-by: Catalin Marinas