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,
linux-arm-kernel@lists.infradead.org,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 1/7] arm64: Split unwind_init()
Date: Tue, 10 May 2022 19:15:04 +0100 [thread overview]
Message-ID: <YnqrqI/Xdq9RMwoc@sirena.org.uk> (raw)
In-Reply-To: <20220413140528.3815-2-madvenka@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Wed, Apr 13, 2022 at 09:05:22AM -0500, madvenka@linux.microsoft.com wrote:
> From: "Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>
>
> unwind_init() is currently a single function that initializes all of the
> unwind state. Split it into the following functions and call them
> appropriately:
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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,
linux-arm-kernel@lists.infradead.org,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 1/7] arm64: Split unwind_init()
Date: Tue, 10 May 2022 19:15:04 +0100 [thread overview]
Message-ID: <YnqrqI/Xdq9RMwoc@sirena.org.uk> (raw)
In-Reply-To: <20220413140528.3815-2-madvenka@linux.microsoft.com>
[-- Attachment #1.1: Type: text/plain, Size: 361 bytes --]
On Wed, Apr 13, 2022 at 09:05:22AM -0500, madvenka@linux.microsoft.com wrote:
> From: "Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>
>
> unwind_init() is currently a single function that initializes all of the
> unwind state. Split it into the following functions and call them
> appropriately:
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-10 18:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f460a35f88195413bcf7305e5083480aab3ca858>
2022-04-13 14:05 ` [PATCH v14 0/7] arm64: Reorganize the unwinder and implement stack trace reliability checks madvenka
2022-04-13 14:05 ` madvenka
2022-04-13 14:05 ` [PATCH v14 1/7] arm64: Split unwind_init() madvenka
2022-04-13 14:05 ` madvenka
2022-05-10 18:15 ` Mark Brown [this message]
2022-05-10 18:15 ` Mark Brown
2022-05-18 5:20 ` Madhavan T. Venkataraman
2022-05-18 5:20 ` Madhavan T. Venkataraman
2022-04-13 14:05 ` [PATCH v14 2/7] arm64: Copy the task argument to unwind_state madvenka
2022-04-13 14:05 ` madvenka
2022-05-10 18:18 ` Mark Brown
2022-05-10 18:18 ` Mark Brown
2022-05-18 5:21 ` Madhavan T. Venkataraman
2022-05-18 5:21 ` Madhavan T. Venkataraman
2022-04-13 14:05 ` [PATCH v14 3/7] arm64: Make the unwind loop in unwind() similar to other architectures madvenka
2022-04-13 14:05 ` madvenka
2022-04-13 14:05 ` [PATCH v14 4/7] arm64: Introduce stack trace reliability checks in the unwinder madvenka
2022-04-13 14:05 ` madvenka
2022-04-13 14:05 ` [PATCH v14 5/7] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka
2022-04-13 14:05 ` madvenka
2022-04-13 14:05 ` [PATCH v14 6/7] arm64: Introduce arch_stack_walk_reliable() madvenka
2022-04-13 14:05 ` madvenka
2022-04-13 14:05 ` [PATCH v14 7/7] arm64: Select HAVE_RELIABLE_STACKTRACE madvenka
2022-04-13 14:05 ` madvenka
2022-04-13 14:11 ` [PATCH v14 0/7] arm64: Reorganize the unwinder and implement stack trace reliability checks Madhavan T. Venkataraman
2022-04-13 14:11 ` Madhavan T. Venkataraman
2022-06-02 22:40 ` Madhavan T. Venkataraman
2022-06-02 22:40 ` Madhavan T. Venkataraman
2022-06-14 17:48 ` Mark Brown
2022-06-14 17:48 ` Mark Brown
2022-06-15 19:19 ` Madhavan T. Venkataraman
2022-06-15 19:19 ` 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=YnqrqI/Xdq9RMwoc@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=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=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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.