From: Marc Zyngier <maz@kernel.org>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: oupton@kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev, catalin.marinas@arm.com, will@kernel.org,
rostedt@goodmis.org, mhiramat@kernel.org,
alexandru.elisei@arm.com, vdonnefort@google.com,
joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, qperret@google.com, ardb@kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 10/11] KVM: arm64: nVHE: Check hypercall handlers against the declared ABI
Date: Tue, 04 Aug 2026 09:47:40 +0100 [thread overview]
Message-ID: <86pkzyb7bn.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+EHjTw1=xCPugZrmQ3nj1ddvCZ=vcZT3=KO_FMHB1USUTu7kA@mail.gmail.com>
On Mon, 03 Aug 2026 19:34:52 +0100,
Fuad Tabba <fuad.tabba@linux.dev> wrote:
>
> On Mon, 3 Aug 2026 at 19:03, Marc Zyngier <maz@kernel.org> wrote:
> ...
> >
> > I've also dropped this with the following hacks. The set_cpu_reg()
> > stuff isn't brilliant, and requires a single word type. But I find the
> > overall scheme less invasive.
> >
> > WDYT?
>
> Works, and hyp-main.nvhe.o comes out byte identical. I did look for a
> way to dispatch on void without the type table, but _Generic doesn't
> take an incomplete type and __builtin_choose_expr type-checks both
> arms on gcc and clang, so I don't think there's a better option.
>
> One nit: the declaration in kvm_hcall.h still says "unsigned long"
> while the definition now says "ulong". Could we make both ulong?
Yeah, that's an oversight. I don't like the ulong stuff at all, but I
don't see how to do this without it.
>
> I'm happy to respin with both of these, or would you like to fold them in?
Oliver is in charge of 7.3, so I'll let him reply on this.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-08-04 8:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 12:42 [PATCH v2 00/11] KVM: arm64: Restore type-checking across the host/hyp hypercall boundary Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 01/11] tracing: Include linux/types.h in trace_remote_event.h Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 02/11] KVM: arm64: nVHE: Share the stacktrace per-CPU declarations with EL2 Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 03/11] KVM: arm64: nVHE: Declare the hyp event IDs before defining them Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 04/11] KVM: arm64: nVHE: Use NULL to reset the trace buffer backing pointer Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 05/11] KVM: arm64: nVHE: Run the source checker under C=2 Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 06/11] arm64: pi: Run the source checker on the libfdt objects " Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 07/11] KVM: arm64: nVHE: Pass host VA arguments as pointers Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 08/11] KVM: arm64: Move the host hypercall interface to its own header Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 09/11] KVM: arm64: Type-check hypercall arguments at the caller Fuad Tabba
2026-08-03 17:59 ` Marc Zyngier
2026-08-03 18:33 ` Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 10/11] KVM: arm64: nVHE: Check hypercall handlers against the declared ABI Fuad Tabba
2026-08-03 18:03 ` Marc Zyngier
2026-08-03 18:34 ` Fuad Tabba
2026-08-04 8:47 ` Marc Zyngier [this message]
2026-08-04 8:50 ` Fuad Tabba
2026-08-03 12:42 ` [PATCH v2 11/11] KVM: arm64: Tag host-VA hypercall parameters __kern Fuad Tabba
2026-08-03 13:44 ` sashiko-bot
2026-08-03 13:49 ` 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=86pkzyb7bn.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oupton@kernel.org \
--cc=qperret@google.com \
--cc=rostedt@goodmis.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 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.