linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
	Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>,
	broonie@kernel.org, madvenka@linux.microsoft.com,
	tabba@google.com, maz@kernel.org, james.morse@arm.com,
	kaleshsingh@google.com
Subject: Re: [PATCH v4 0/9] arm64: stacktrace: cleanups and improvements
Date: Fri,  9 Sep 2022 19:08:14 +0100	[thread overview]
Message-ID: <166274688793.1012078.10060780650363511226.b4-ty@arm.com> (raw)
In-Reply-To: <20220901130646.1316937-1-mark.rutland@arm.com>

On Thu, 1 Sep 2022 14:06:37 +0100, Mark Rutland wrote:
> This series is a set of improvements for the arm64 stacktrace code, atop
> the rework merged for v6.0. I'm hoping this can be queued for v6.1.
> 
> Largely, the series decouples portions of the unwind code, making some
> structural changes that remove the need for coupling (e.g. removing the
> need for the stack type enumeration, and factoring out callbacks). This
> should make it easier to make some further changes I have spoken about
> previously (e.g. adding some metadata to the stack dump output), and I
> have some patches building atop this which I intend to send out once
> this is queued.
> 
> [...]

Applied to arm64 (for-next/stacktrace), thanks!

[1/9] arm64: stacktrace: fix kerneldoc comments
      https://git.kernel.org/arm64/c/16283c54a6c7
[2/9] arm64: stacktrace: simplify unwind_next_common()
      https://git.kernel.org/arm64/c/bc8d75212d73
[3/9] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record()
      https://git.kernel.org/arm64/c/b532ab5f2338
[4/9] arm64: stacktrace: move SDEI stack helpers to stacktrace code
      https://git.kernel.org/arm64/c/75758d511432
[5/9] arm64: stacktrace: add stackinfo_on_stack() helper
      https://git.kernel.org/arm64/c/36f9a8793c16
[6/9] arm64: stacktrace: rework stack boundary discovery
      https://git.kernel.org/arm64/c/d1f684e46bbd
[7/9] arm64: stacktrace: remove stack type from fp translator
      https://git.kernel.org/arm64/c/bd8abd68836b
[8/9] arm64: stacktrace: track all stack boundaries explicitly
      https://git.kernel.org/arm64/c/8df137300d19
[9/9] arm64: stacktrace: track hyp stacks in unwinder's address space
      https://git.kernel.org/arm64/c/4b5e694e25ca

-- 
Catalin


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2022-09-09 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 13:06 [PATCH v4 0/9] arm64: stacktrace: cleanups and improvements Mark Rutland
2022-09-01 13:06 ` [PATCH v4 1/9] arm64: stacktrace: fix kerneldoc comments Mark Rutland
2022-09-01 13:06 ` [PATCH v4 2/9] arm64: stacktrace: simplify unwind_next_common() Mark Rutland
2022-09-01 13:06 ` [PATCH v4 3/9] arm64: stacktrace: rename unwind_next_common() -> unwind_next_frame_record() Mark Rutland
2022-09-01 13:06 ` [PATCH v4 4/9] arm64: stacktrace: move SDEI stack helpers to stacktrace code Mark Rutland
2022-09-01 13:06 ` [PATCH v4 5/9] arm64: stacktrace: add stackinfo_on_stack() helper Mark Rutland
2022-09-01 13:06 ` [PATCH v4 6/9] arm64: stacktrace: rework stack boundary discovery Mark Rutland
2022-09-01 13:06 ` [PATCH v4 7/9] arm64: stacktrace: remove stack type from fp translator Mark Rutland
2022-09-01 13:06 ` [PATCH v4 8/9] arm64: stacktrace: track all stack boundaries explicitly Mark Rutland
2022-09-01 13:06 ` [PATCH v4 9/9] arm64: stacktrace: track hyp stacks in unwinder's address space Mark Rutland
2022-09-09 18:08 ` Catalin Marinas [this message]

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=166274688793.1012078.10060780650363511226.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --cc=james.morse@arm.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=madvenka@linux.microsoft.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=tabba@google.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: link
Be 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).