Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1283489

Re: [PATCH] arm64: ftrace: stop using kstop_machine to enable/disable tracing

From libin <huawei.libin@huawei.com>
Newsgroups linux.kernel
Subject Re: [PATCH] arm64: ftrace: stop using kstop_machine to enable/disable tracing
Date 2015-12-04 02:10 +0100
Message-ID <qBN2P-4ko-37@gated-at.bofh.it> (permalink)
References (2 earlier) <qByn8-34K-9@gated-at.bofh.it> <qBywO-38I-31@gated-at.bofh.it> <qBDGa-6Nq-15@gated-at.bofh.it> <qBDGa-6Nq-13@gated-at.bofh.it> <qBE9d-6XG-51@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Thanks very much to Will and Steve for the wonderful comments, I will modify the
commit message, and remove the misleading comments about module text
disappearing case.

Thanks again,
Li Bin

on 2015/12/3 23:31, Steven Rostedt wrote:
> On Thu, 3 Dec 2015 15:09:26 +0000
> Will Deacon <will.deacon@arm.com> wrote:
>
>> Yeah, I think the comments on x86 and arm64 are out of date. They also
>> mention the freeing of __init sections -- is that still a concern?
> No we black list them, any section that we are not sure will be there
> when we expect it to has recordmcount.c nop out the calls to mcount and
> they are ignored. Remember the e1000e bug? This was the reproducer.
>
> Anyway, on my todo list is to allow init sections to be traced. To do
> so would mean that I need to add generic code that lets ftrace know to
> remove init sections at boot up. Right now (or at least the last time I
> checked, which was back in 2009), every arch had its own way of freeing
> init memory. If that has changed, or I can just place a hook where it
> happens (which is probably the easy part), I can allow init code to be
> traced too.
>
> -- Steve
>
>
> .
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Will Deacon <will.deacon@arm.com> - 2015-12-02 13:40 +0100
  Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Will Deacon <will.deacon@arm.com> - 2015-12-02 14:20 +0100
    Re: [PATCH] arm64: ftrace: stop using kstop_machine to enable/disable  tracing libin <huawei.libin@huawei.com> - 2015-12-03 10:50 +0100
      Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Will Deacon <will.deacon@arm.com> - 2015-12-03 12:50 +0100
        Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Steven Rostedt <rostedt@goodmis.org> - 2015-12-03 16:10 +0100
  Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Steven Rostedt <rostedt@goodmis.org> - 2015-12-02 15:10 +0100
  Re: [PATCH] arm64: ftrace: stop using kstop_machine to enable/disable  tracing libin <huawei.libin@huawei.com> - 2015-12-03 10:30 +0100
    Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Will Deacon <will.deacon@arm.com> - 2015-12-03 10:40 +0100
      Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Will Deacon <will.deacon@arm.com> - 2015-12-03 16:10 +0100
        Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Steven Rostedt <rostedt@goodmis.org> - 2015-12-03 16:40 +0100
          Re: [PATCH] arm64: ftrace: stop using kstop_machine to enable/disable  tracing libin <huawei.libin@huawei.com> - 2015-12-04 02:10 +0100
      Re: [PATCH] arm64: ftrace: stop using kstop_machine to  enable/disable tracing Steven Rostedt <rostedt@goodmis.org> - 2015-12-03 16:10 +0100

csiph-web