Re: [PATCH 3/7] uprobes: Introduce uprobe_apply()

2013-02-11 Thread Srikar Dronamraju
* Oleg Nesterov [2013-02-04 20:02:50]: > Currently it is not possible to change the filtering constraints after > uprobe_register(), so a consumer can not, say, start to trace a task/mm > which was previously filtered out, or remove the no longer needed bp's. > > Introduce uprobe_apply() which

Re: [PATCH 3/7] uprobes: Introduce uprobe_apply()

2013-02-11 Thread Srikar Dronamraju
* Oleg Nesterov o...@redhat.com [2013-02-04 20:02:50]: Currently it is not possible to change the filtering constraints after uprobe_register(), so a consumer can not, say, start to trace a task/mm which was previously filtered out, or remove the no longer needed bp's. Introduce

[PATCH 3/7] uprobes: Introduce uprobe_apply()

2013-02-04 Thread Oleg Nesterov
Currently it is not possible to change the filtering constraints after uprobe_register(), so a consumer can not, say, start to trace a task/mm which was previously filtered out, or remove the no longer needed bp's. Introduce uprobe_apply() which simply does register_for_each_vma() again to

[PATCH 3/7] uprobes: Introduce uprobe_apply()

2013-02-04 Thread Oleg Nesterov
Currently it is not possible to change the filtering constraints after uprobe_register(), so a consumer can not, say, start to trace a task/mm which was previously filtered out, or remove the no longer needed bp's. Introduce uprobe_apply() which simply does register_for_each_vma() again to