From: Vincent Donnefort <vdonnefort@google.com>
To: Fuad Tabba <tabba@google.com>
Cc: maz@kernel.org, oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, will@kernel.org, rostedt@goodmis.org,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kernel-team@android.com
Subject: Re: [PATCH v1 1/4] KVM: arm64: Allow early calls to pKVM host_share/unshare_hyp
Date: Tue, 7 Jul 2026 17:53:30 +0100 [thread overview]
Message-ID: <ak0vCmPyTlWIwFEI@google.com> (raw)
In-Reply-To: <CA+EHjTwSU67aNdgWvgR3ZGSB07Hu7wt4rUBkVGhrhoHKa_S1vw@mail.gmail.com>
On Sun, Jun 14, 2026 at 02:39:30PM +0100, Fuad Tabba wrote:
> On Fri, 12 Jun 2026 at 15:22, Vincent Donnefort <vdonnefort@google.com> wrote:
> >
> > The hypervisor tracing for pKVM relies on the __pkvm_host_share_hyp and
> > __pkvm_host_unshare_hyp HVCs. In order to start tracing as early as
> > possible, allow those two HVCs before the host is deprivileged.
> >
> > Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
>
> To my good friend Sashiko:
> https://lore.kernel.org/all/20260529121755.2923500-1-tabba@google.com/
>
> The hyp_trace_load() issue seems legit though.
I've just posted lore.kernel.org/all/20260707165029.3410701-1-vdonnefort@google.com
>
> As for this patch itself:
>
> Reviewed-by: Fuad Tabba <tabba@google.com>
> Tested-by: Fuad Tabba <tabba@google.com>
>
> Cheers,
> /fuad
>
>
> >
> > diff --git a/arch/arm64/include/asm/kvm_asm.h b/arch/arm64/include/asm/kvm_asm.h
> > index 043495f7fc78..fb049c40d04f 100644
> > --- a/arch/arm64/include/asm/kvm_asm.h
> > +++ b/arch/arm64/include/asm/kvm_asm.h
> > @@ -89,12 +89,12 @@ enum __kvm_host_smccc_func {
> > __KVM_HOST_SMCCC_FUNC___vgic_v3_restore_vmcr_aprs,
> > __KVM_HOST_SMCCC_FUNC___vgic_v5_save_apr,
> > __KVM_HOST_SMCCC_FUNC___vgic_v5_restore_vmcr_apr,
> > + __KVM_HOST_SMCCC_FUNC___pkvm_host_share_hyp,
> > + __KVM_HOST_SMCCC_FUNC___pkvm_host_unshare_hyp,
> >
> > MARKER(__KVM_HOST_SMCCC_FUNC_PKVM_ONLY),
> >
> > /* Hypercalls that are available only when pKVM has finalised. */
> > - __KVM_HOST_SMCCC_FUNC___pkvm_host_share_hyp,
> > - __KVM_HOST_SMCCC_FUNC___pkvm_host_unshare_hyp,
> > __KVM_HOST_SMCCC_FUNC___pkvm_host_donate_guest,
> > __KVM_HOST_SMCCC_FUNC___pkvm_host_share_guest,
> > __KVM_HOST_SMCCC_FUNC___pkvm_host_unshare_guest,
> > diff --git a/arch/arm64/kvm/hyp/nvhe/hyp-main.c b/arch/arm64/kvm/hyp/nvhe/hyp-main.c
> > index 06db299c37a8..f0c52667cf52 100644
> > --- a/arch/arm64/kvm/hyp/nvhe/hyp-main.c
> > +++ b/arch/arm64/kvm/hyp/nvhe/hyp-main.c
> > @@ -721,9 +721,9 @@ static const hcall_t host_hcall[] = {
> > HANDLE_FUNC(__vgic_v3_restore_vmcr_aprs),
> > HANDLE_FUNC(__vgic_v5_save_apr),
> > HANDLE_FUNC(__vgic_v5_restore_vmcr_apr),
> > -
> > HANDLE_FUNC(__pkvm_host_share_hyp),
> > HANDLE_FUNC(__pkvm_host_unshare_hyp),
> > +
> > HANDLE_FUNC(__pkvm_host_donate_guest),
> > HANDLE_FUNC(__pkvm_host_share_guest),
> > HANDLE_FUNC(__pkvm_host_unshare_guest),
> > --
> > 2.54.0.1136.gdb2ca164c4-goog
> >
next prev parent reply other threads:[~2026-07-07 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 14:22 [PATCH v1 0/4] trace_hyp_printk() for pKVM/nVHE hypervisor Vincent Donnefort
2026-06-12 14:22 ` [PATCH v1 1/4] KVM: arm64: Allow early calls to pKVM host_share/unshare_hyp Vincent Donnefort
2026-06-14 13:39 ` Fuad Tabba
2026-07-07 16:53 ` Vincent Donnefort [this message]
2026-06-12 14:22 ` [PATCH v1 2/4] KVM: arm64: Move kvm_define_hypevents.h to arch/arm64/kvm/ Vincent Donnefort
2026-06-14 13:41 ` Fuad Tabba
2026-06-12 14:22 ` [PATCH v1 3/4] tracing/remotes: Add REMOTE_EVENT_CUSTOM_PRINTK() helper Vincent Donnefort
2026-06-14 14:46 ` Fuad Tabba
2026-06-12 14:22 ` [PATCH v1 4/4] KVM: arm64: Add hyp_printk event to nVHE/pKVM hyp Vincent Donnefort
2026-06-14 15:25 ` Fuad Tabba
2026-06-15 8:29 ` Vincent Donnefort
2026-06-14 12:57 ` [PATCH v1 0/4] trace_hyp_printk() for pKVM/nVHE hypervisor Fuad Tabba
2026-06-15 8:27 ` Vincent Donnefort
2026-06-15 8:30 ` Fuad Tabba
2026-06-15 8:57 ` Fuad Tabba
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=ak0vCmPyTlWIwFEI@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@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