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: N, Soumya P
Date: Sat May 21 2016 - 14:45:45 EST

Next message: Michal Nazarewicz: "[PATCH 1/2] usb: gadget: f_fs: printk error when excess data is dropped on read"
Previous message: Bjorn Andersson: "Re: [PATCH v8 2/4] power: reset: add reboot mode driver"
In reply to: 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."
Next in thread: Soumya PN: "[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.
>

>>No need, I just pulled in your patch and made the updates to the change log and subject myself. I'm starting my tests on it now.

> Thanks Steve.

Next message: Michal Nazarewicz: "[PATCH 1/2] usb: gadget: f_fs: printk error when excess data is dropped on read"
Previous message: Bjorn Andersson: "Re: [PATCH v8 2/4] power: reset: add reboot mode driver"
In reply to: 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."
Next in thread: Soumya PN: "[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 ]