Mark Kettenis <mark.kettenis@xs4all.nl> wrote:

> > Date: Sun, 13 Jul 2025 16:22:03 +1000
> > From: David Gwynne <david@gwynne.id.au>
> > 
> > a driver can depend on xcall and get this glue code compiled so it will
> > work on arm64.
> > 
> > ok?
> 
> So what's the way forward here.  Theo objected to the extent of the
> '#ifdef NXCALL > 0' and I think and then the discussion died?  I'm not
> a fan of that either, but we also don't want that code in RAMDISK
> kernels if we don't need it.  So perhaps just drop those here and make
> the xcall stuff non-optional for MULTIPROCESSOR kernels?

That is my thought also.  If this is impossible to use without setting
an option, then noone will use it.  If noone is using it, then why have
the code at all?  I think we want it, because we know we need it (soon).