[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzWKE=6N4_0ihV4JbFcAXJaO_E_=V4q9M2npk3CJM0yrQ@mail.gmail.com>
Date: Thu, 22 Mar 2018 13:52:34 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Alexei Starovoitov <ast@...com>,
David Miller <davem@...emloft.net>,
Daniel Borkmann <daniel@...earbox.net>,
Peter Zijlstra <peterz@...radead.org>,
Network Development <netdev@...r.kernel.org>,
kernel-team <kernel-team@...com>,
Linux API <linux-api@...r.kernel.org>
Subject: Re: [PATCH v3 bpf-next 01/10] treewide: remove struct-pass-by-value
from tracepoints arguments
On Thu, Mar 22, 2018 at 1:48 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> OK, but instead of changing it to pass by reference, why not just pass
> the value. That is:
>
> static void xen_set_pte_atomic(pte_t *ptep, pte_t pte)
> {
> - trace_xen_mmu_set_pte_atomic(ptep, pte);
> + trace_xen_mmu_set_pte_atomic(ptep, native_pte_val(pte));
> set_64bit((u64 *)ptep, native_pte_val(pte));
> }
That looks simple and clean, and makes sense since the function itself
then uses that value anyway.
Certainly simpler than my monster define.
Linus
Powered by blists - more mailing lists