From: Marc Zyngier <maz@kernel.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: oupton@kernel.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, 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,
qperret@google.com
Subject: Re: [PATCH v1 0/3] KVM: arm64: pkvm: Extend hypervisor entering tracing reasons
Date: Fri, 09 Oct 2026 14:50:23 +0100 [thread overview]
Message-ID: <867bjr2db4.wl-maz@kernel.org> (raw)
In-Reply-To: <20261009084529.462577-1-vdonnefort@google.com>
On Fri, 09 Oct 2026 09:45:26 +0100,
Vincent Donnefort <vdonnefort@google.com> wrote:
>
> This series make the hyp_enter event more detailed by adding a "from="
> field and by using the ESR class when relevant. This is interesting for
> example to know when the guest has exited for an HVC.
None of that seems to qualify as a fix, and I've now closed the tree
to any new feature.
Please come back after -rc1!
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-10-09 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 8:45 [PATCH v1 0/3] KVM: arm64: pkvm: Extend hypervisor entering tracing reasons Vincent Donnefort
2026-10-09 8:45 ` [PATCH v1 1/3] KVM: arm64: Add ESR class to the hyp_enter hyp event Vincent Donnefort
2026-10-09 11:30 ` Fuad Tabba
2026-10-09 13:02 ` Vincent Donnefort
2026-10-09 14:08 ` Fuad Tabba
2026-10-09 8:45 ` [PATCH v1 2/3] KVM: arm64: Add guest_hvc " Vincent Donnefort
2026-10-09 12:06 ` Fuad Tabba
2026-10-09 13:17 ` Vincent Donnefort
2026-10-09 8:45 ` [PATCH v1 3/3] KVM: arm64: Add host_hvc " Vincent Donnefort
2026-10-09 12:26 ` Fuad Tabba
2026-10-09 13:20 ` Vincent Donnefort
2026-10-09 13:50 ` 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=867bjr2db4.wl-maz@kernel.org \
--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=qperret@google.com \
--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