Re: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts.

From: Steven Rostedt
Date: Thu May 19 2016 - 09:57:55 EST

Next message: Muhammad Falak R Wani: "[PATCH] brcmfmac: use kmemdup"
Previous message: Paolo Bonzini: "Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon"
In reply to: N, Soumya P: "RE: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts."
Next in thread: Steven Rostedt: "Re: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 19 May 2016 13:49:16 +0000
"N, Soumya P" <soumya.p.n@xxxxxxx> wrote:

> Hi Steve,
>
> Thanks for the explanation.
> I will take care of your comments and send v2 of the same patch.
>

I'll also note that in our forum (LKML), we do not do "top posting".

We practice "inline replying" and "trimming". See

https://en.wikipedia.org/wiki/Posting_style

-- Steve

Next message: Muhammad Falak R Wani: "[PATCH] brcmfmac: use kmemdup"
Previous message: Paolo Bonzini: "Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon"
In reply to: N, Soumya P: "RE: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts."
Next in thread: Steven Rostedt: "Re: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]