[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.21.1911131500210.18679@pobox.suse.cz>
Date: Wed, 13 Nov 2019 15:13:44 +0100 (CET)
From: Miroslav Benes <mbenes@...e.cz>
To: Steven Rostedt <rostedt@...dmis.org>
cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
X86 ML <x86@...nel.org>, Nadav Amit <nadav.amit@...il.com>,
Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Song Liu <songliubraving@...com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [PATCH 03/10] ftrace: Add register_ftrace_direct()
> @@ -1757,6 +1761,18 @@ static bool __ftrace_hash_rec_update(struct ftrace_ops *ops,
> return false;
> rec->flags--;
>
> + if (ops->flags & FTRACE_OPS_FL_DIRECT)
> + rec->flags &= ~FTRACE_FL_DIRECT;
> +
> + /*
> + * Only the internal direct_ops should have the
> + * DIRECT flag set. Thus, if it is removing a
> + * function, then that function should no longer
> + * be direct.
> + */
> + if (ops->flags & FTRACE_OPS_FL_DIRECT)
> + rec->flags &= ~FTRACE_FL_DIRECT;
> +
The flag is dropped twice here.
Miroslav
Powered by blists - more mailing lists