From: Marc Zyngier <maz@kernel.org>
To: tabba@google.com, oliver.upton@linux.dev, broonie@kernel.org,
Kalesh Singh <kaleshsingh@google.com>,
mark.rutland@arm.com, madvenka@linux.microsoft.com
Cc: andreyknvl@gmail.com, kvmarm@lists.cs.columbia.edu,
will@kernel.org, wangkefeng.wang@huawei.com,
catalin.marinas@arm.com, vincenzo.frascino@arm.com,
ast@kernel.org, kernel-team@android.com, elver@google.com,
mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, android-mm@google.com
Subject: Re: [PATCH v6 00/17] KVM nVHE Hypervisor stack unwinder
Date: Wed, 27 Jul 2022 18:44:53 +0100 [thread overview]
Message-ID: <165894387426.1300284.3994289980983137161.b4-ty@kernel.org> (raw)
In-Reply-To: <20220726073750.3219117-1-kaleshsingh@google.com>
On Tue, 26 Jul 2022 00:37:33 -0700, Kalesh Singh wrote:
> This is v6 of nVHE stacktrace support. The series is based on
> arm64 for-next/stacktrace.
>
> The previous versions were posted at:
> v5: https://lore.kernel.org/r/20220721055728.718573-1-kaleshsingh@google.com/
> v4: https://lore.kernel.org/r/20220715061027.1612149-1-kaleshsingh@google.com/
> v3: https://lore.kernel.org/r/20220607165105.639716-1-kaleshsingh@google.com/
> v2: https://lore.kernel.org/r/20220502191222.4192768-1-kaleshsingh@google.com/
> v1: https://lore.kernel.org/r/20220427184716.1949239-1-kaleshsingh@google.com/
>
> [...]
Applied to next, thanks!
[01/17] arm64: stacktrace: Add shared header for common stack unwinding code
commit: 6bf212c89c48458d8deef1c973678c62528dab04
[02/17] arm64: stacktrace: Factor out on_accessible_stack_common()
commit: 15a59f19a015185bff90a68f601caec151dea4b4
[03/17] arm64: stacktrace: Factor out unwind_next_common()
commit: be63c647fd28d25484257f5f36a008db7d99991d
[04/17] arm64: stacktrace: Handle frame pointer from different address spaces
commit: 5b1b08619f50422c3e43d1fd7af257595a9e4a67
[05/17] arm64: stacktrace: Factor out common unwind()
commit: f51e7146740514347d6c5526a2c393e224a19c0d
[06/17] arm64: stacktrace: Add description of stacktrace/common.h
commit: 051ece6758cc10c2a6f1700ffe86d23fbb0b2553
[07/17] KVM: arm64: On stack overflow switch to hyp overflow_stack
commit: 548ec3336f323db56260b312c232ab37285f0284
[08/17] KVM: arm64: Stub implementation of non-protected nVHE HYP stack unwinder
commit: 573e1e8275f7167ddd533c6e4e0f500f8be4d974
[09/17] KVM: arm64: Prepare non-protected nVHE hypervisor stacktrace
commit: 879e5ac7b2e4db05799a905b5a07fc9e5dedf651
[10/17] KVM: arm64: Implement non-protected nVHE hyp stack unwinder
commit: db129d486ebdf4e3168282236f9d9008b42cac7e
[11/17] KVM: arm64: Introduce hyp_dump_backtrace()
commit: 314a61dc31845c233e47c53db3fe6f34284034f4
[12/17] KVM: arm64: Add PROTECTED_NVHE_STACKTRACE Kconfig
commit: 72adac1bd234002a65cef738e0eebfd6c2ce2e30
[13/17] KVM: arm64: Allocate shared pKVM hyp stacktrace buffers
commit: 6928bcc84bc4bd9a24a1cb1986418c3de76e1d99
[14/17] KVM: arm64: Stub implementation of pKVM HYP stack unwinder
commit: 25aa73b6db1831527cd4f14bf0ddf8dceadec802
[15/17] KVM: arm64: Save protected-nVHE (pKVM) hyp stacktrace
commit: 871c5d931417d3c0e1aa32c9e04da1dc74703843
[16/17] KVM: arm64: Implement protected nVHE hyp stack unwinder
commit: 75e9459e48d4867caf549e388bd4faabe1dbcbd3
[17/17] KVM: arm64: Introduce pkvm_dump_backtrace()
commit: 3a7e1b55aad45c0cf86bd4e2f212bb9a61905142
Cheers,
M.
--
Marc Zyngier <maz@kernel.org>
prev parent reply other threads:[~2022-07-27 18:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 7:37 Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 01/17] arm64: stacktrace: Add shared header for common stack unwinding code Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 02/17] arm64: stacktrace: Factor out on_accessible_stack_common() Kalesh Singh
2022-07-26 16:01 ` Marc Zyngier
2022-07-26 16:33 ` Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 03/17] arm64: stacktrace: Factor out unwind_next_common() Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 04/17] arm64: stacktrace: Handle frame pointer from different address spaces Kalesh Singh
2022-07-26 14:34 ` Mark Brown
2022-07-26 15:30 ` Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 05/17] arm64: stacktrace: Factor out common unwind() Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 06/17] arm64: stacktrace: Add description of stacktrace/common.h Kalesh Singh
2022-07-26 14:49 ` Mark Brown
2022-07-26 7:37 ` [PATCH v6 07/17] KVM: arm64: On stack overflow switch to hyp overflow_stack Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 08/17] KVM: arm64: Stub implementation of non-protected nVHE HYP stack unwinder Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 09/17] KVM: arm64: Prepare non-protected nVHE hypervisor stacktrace Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 10/17] KVM: arm64: Implement non-protected nVHE hyp stack unwinder Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 11/17] KVM: arm64: Introduce hyp_dump_backtrace() Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 12/17] KVM: arm64: Add PROTECTED_NVHE_STACKTRACE Kconfig Kalesh Singh
2022-07-26 10:00 ` Marc Zyngier
2022-07-26 15:33 ` Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 13/17] KVM: arm64: Allocate shared pKVM hyp stacktrace buffers Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 14/17] KVM: arm64: Stub implementation of pKVM HYP stack unwinder Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 15/17] KVM: arm64: Save protected-nVHE (pKVM) hyp stacktrace Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 16/17] KVM: arm64: Implement protected nVHE hyp stack unwinder Kalesh Singh
2022-07-26 7:37 ` [PATCH v6 17/17] KVM: arm64: Introduce pkvm_dump_backtrace() Kalesh Singh
2022-07-27 17:44 ` Marc Zyngier [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=165894387426.1300284.3994289980983137161.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=andreyknvl@gmail.com \
--cc=android-mm@google.com \
--cc=ast@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=elver@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=tabba@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=wangkefeng.wang@huawei.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
all inboxes | Powered by JetHome®