> >> > -static noinline int __invoke_psci_fn_hvc(u64 function_id, u64 arg0, u64
> >> > arg1,
> >> > +static noinline notrace int __invoke_psci_fn_hvc(u64 function_id, u64
> >> > arg0, u64 arg1,
> >> > u64 arg2)
[...]
> >> > -static noinline int __invoke_psci_fn_smc(u64 function_id, u64 arg0, u64
> >> > arg1,
> >> > +static noinline notrace int __invoke_psci_fn_smc(u64 function_id, u64
> >> > arg0, u64 arg1,
> >> > u64 arg2)
[...]
> > As I mentioned in my reply, Will was waiting for -rc1 to post our
> > patches (which move this out to asm for arm and arm64). He's out of the
> > office today, but I expect they will be posted tomorrow (and hopefully
> > queued shortly thereafter).
> >
> > Mark.
[...]
> Hi,
>
> I notice that the mainline kernel moved these psci calls to a separate
> file but I
> was wondering how can it guarantee that the function register
> placement will hold?
The commit in question [1] moves the issuing of the HVC and SMC into an
assembly file, and the C code calls these as opaque functions.
Due to this the compiler *must* respect the AAPCS and place the values
into the expected registers (x0 to x3).
> If you build the kernel with -O0 some function register allocation changes as
> opposed to -O2 or if you use another compiler such as Clang.
Surely this is only true if all the functions live in the same
compilation unit? Or perhaps with LTO (surely this cannot modify
assembly which was not generated by the compiler)?
If the compiler is rearranging registers for a function call it knows
nothing about, in violation of the AAPCS, then that compiler sounds
broken.
> In LLVMLinux we solved this by using one of Andy's solution which is
> to use register placement:
>
> register u32 function_id_r0 asm ("r0") = function_id;
> register u32 arg0_r1 asm ("r1") = arg0;
> register u32 arg1_r2 asm ("r2") = arg1;
> register u32 arg2_r3 asm ("r3") = arg2;
Surely this is only necessary when the call issuing function is
implemented in C?
Mark.
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f5e0a12ca2d939e47995f73428d9bf1ad372b289
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
