Hi Mark,
thank you for your very detailed feedback, I'll incorporate it
all into the next version, besides one issue:
On Tue, Oct 02, 2018 at 12:27:41PM +0100, Mark Rutland wrote:
>
> Please use the insn framework, as we do to generate all the other
> instruction sequences in ftrace.
>
> MOV (register) is an alias of ORR (shifted register), i.e.
>
> mov <xd>, <xm>
>
> ... is:
>
> orr <xd>, xzr, <xm>
>
> ... and we have code to generate ORR, so we can add a trivial wrapper to
> generate MOV.
I had something similar in v2; but it was hardly any better to read or
understand. My main question however is: how do you justify the runtime
overhead of aarch64_insn_gen_logical_shifted_reg for every function that
gets its tracing switched on or off? The result is always the same 4-byte
constant, so why not use a macro and a comment that says what it does?
Torsten
