From: Marc Zyngier <maz@kernel.org>
To: oupton@kernel.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Vincent Donnefort <vdonnefort@google.com>
Cc: joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org,
kernel-team@android.com, fuad.tabba@linux.dev
Subject: Re: [PATCH v5 0/4] trace_hyp_printk() for pKVM/nVHE hypervisor
Date: Sat, 3 Oct 2026 10:27:08 +0100 [thread overview]
Message-ID: <179101962008.602721.42919125204106176.b4-ty@b4> (raw)
In-Reply-To: <20261001143000.3371786-1-vdonnefort@google.com>
On Thu, 01 Oct 2026 15:29:56 +0100, Vincent Donnefort wrote:
> This series adds a hypervisor event "hyp_printk" which enables
> developers to log pretty much anything into the hypervisor tracing
> buffer, just like the kernel function trace_printk().
>
> This enables rich logging from the hypervisor, while leaving all the
> string parsing burden to the kernel. This has been the main way of
> debugging pKVM in Android.
>
> [...]
Applied to next, thanks!
[1/4] KVM: arm64: Allow early calls to pKVM host_share/unshare_hyp
commit: d35311c5d66095da3949787064d4738fee435d67
[2/4] KVM: arm64: Move kvm_define_hypevents.h to arch/arm64/kvm/
commit: 955feee93e037af78caed7e98d29bbf0268420b0
[3/4] tracing/remotes: Add REMOTE_EVENT_CUSTOM_PRINTK() helper
commit: 604aaeb39521ef70f56c036dc065b133c85f06aa
[4/4] KVM: arm64: Add hyp_printk event to nVHE/pKVM hyp
commit: 92866564020c2fbede7f77f5957a75f11f931d53
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-10-03 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 14:29 [PATCH v5 0/4] trace_hyp_printk() for pKVM/nVHE hypervisor Vincent Donnefort
2026-10-01 14:29 ` [PATCH v5 1/4] KVM: arm64: Allow early calls to pKVM host_share/unshare_hyp Vincent Donnefort
2026-10-01 14:29 ` [PATCH v5 2/4] KVM: arm64: Move kvm_define_hypevents.h to arch/arm64/kvm/ Vincent Donnefort
2026-10-01 14:29 ` [PATCH v5 3/4] tracing/remotes: Add REMOTE_EVENT_CUSTOM_PRINTK() helper Vincent Donnefort
2026-10-01 14:30 ` [PATCH v5 4/4] KVM: arm64: Add hyp_printk event to nVHE/pKVM hyp Vincent Donnefort
2026-10-03 9:27 ` 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=179101962008.602721.42919125204106176.b4-ty@b4 \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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