LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org> To: madvenka@linux.microsoft.com Cc: mark.rutland@arm.com, jpoimboe@redhat.com, ardb@kernel.org, nobuta.keiya@fujitsu.com, sjitindarsingh@gmail.com, catalin.marinas@arm.com, will@kernel.org, jmorris@namei.org, pasha.tatashin@soleen.com, jthierry@redhat.com, linux-arm-kernel@lists.infradead.org, live-patching@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v8 2/4] arm64: Reorganize the unwinder code for better consistency and maintenance Date: Thu, 26 Aug 2021 16:46:34 +0100 [thread overview] Message-ID: <YSe3WogpFIu97i/7@sirena.org.uk> (raw) In-Reply-To: <20210812190603.25326-3-madvenka@linux.microsoft.com> [-- Attachment #1: Type: text/plain, Size: 1074 bytes --] On Thu, Aug 12, 2021 at 02:06:01PM -0500, madvenka@linux.microsoft.com wrote: > Renaming of unwinder functions > ============================== > Rename unwinder functions to unwind_*() similar to other architectures > for naming consistency. More on this below. This feels like it could probably do with splitting up a bit for reviewability, several of these headers you've got in the commit logs look like they could be separate commits. Splitting things up does help with reviewability, having only one change to keep in mind at once is a lot less cognative load. > Replace walk_stackframe() with unwind() > ======================================= > > walk_stackframe() contains the unwinder loop that walks the stack > frames. Currently, start_backtrace() and walk_stackframe() are called > separately. They should be combined in the same function. Also, the > loop in walk_stackframe() should be simplified and should look like > the unwind loops in other architectures such as X86 and S390. This definitely seems like a separate change. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-26 16:24 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <b45aac2843f16ca759e065ea547ab0afff8c0f01> 2021-08-12 19:05 ` [RFC PATCH v8 0/4] arm64: Reorganize the unwinder and implement stack trace reliability checks madvenka 2021-08-12 19:06 ` [RFC PATCH v8 1/4] arm64: Make all stack walking functions use arch_stack_walk() madvenka 2021-08-24 13:13 ` Mark Rutland 2021-08-24 17:21 ` Madhavan T. Venkataraman 2021-08-24 17:38 ` Madhavan T. Venkataraman 2021-08-24 17:38 ` Mark Brown 2021-08-24 17:40 ` Madhavan T. Venkataraman 2021-08-26 4:52 ` Madhavan T. Venkataraman 2021-10-09 23:41 ` Madhavan T. Venkataraman 2021-08-12 19:06 ` [RFC PATCH v8 2/4] arm64: Reorganize the unwinder code for better consistency and maintenance madvenka 2021-08-26 15:46 ` Mark Brown [this message] 2021-08-26 23:19 ` Madhavan T. Venkataraman 2021-09-01 16:20 ` Mark Brown 2021-09-02 7:10 ` Madhavan T. Venkataraman 2021-08-12 19:06 ` [RFC PATCH v8 3/4] arm64: Introduce stack trace reliability checks in the unwinder madvenka 2021-08-24 5:55 ` nobuta.keiya 2021-08-24 12:19 ` Madhavan T. Venkataraman 2021-08-25 0:01 ` nobuta.keiya 2021-08-26 15:57 ` Mark Brown 2021-08-26 23:31 ` Madhavan T. Venkataraman 2021-08-12 19:06 ` [RFC PATCH v8 4/4] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka 2021-08-12 19:17 ` [RFC PATCH v8 0/4] arm64: Reorganize the unwinder and implement stack trace reliability checks Madhavan T. Venkataraman
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YSe3WogpFIu97i/7@sirena.org.uk \ --to=broonie@kernel.org \ --cc=ardb@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=jmorris@namei.org \ --cc=jpoimboe@redhat.com \ --cc=jthierry@redhat.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=live-patching@vger.kernel.org \ --cc=madvenka@linux.microsoft.com \ --cc=mark.rutland@arm.com \ --cc=nobuta.keiya@fujitsu.com \ --cc=pasha.tatashin@soleen.com \ --cc=sjitindarsingh@gmail.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).