Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752000AbbFZLLZ (ORCPT ); Fri, 26 Jun 2015 07:11:25 -0400 Received: from szxga01-in.huawei.com ([58.251.152.64]:23583 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752167AbbFZLLP (ORCPT ); Fri, 26 Jun 2015 07:11:15 -0400 Message-ID: <558D3307.2080801@huawei.com> Date: Fri, 26 Jun 2015 19:09:59 +0800 From: "Wangnan (F)" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Alexei Starovoitov , , , , , , , , , , CC: , , , , Subject: Re: [RFC PATCH 3/3] perf tools: Support attach BPF program on uprobe events References: <1435228645-116055-1-git-send-email-wangnan0@huawei.com> <1435228645-116055-4-git-send-email-wangnan0@huawei.com> <558D11A4.5020102@plumgrid.com> In-Reply-To: <558D11A4.5020102@plumgrid.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.111.66.109] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 952 Lines: 34 On 2015/6/26 16:47, Alexei Starovoitov wrote: > On 6/25/15 3:37 AM, Wang Nan wrote: >> This patch append new syntax to BPF object section name to support >> probing at uprobe event. Now we can use BPF program like this: >> >> SEC( >> "target:/lib64/libc.so.6\n" >> "libcwrite=__write" >> ) >> int libcwrite(void *ctx) >> { >> return 1; >> } >> >> Where, in section name of a program, before the main config string, >> we can use 'key:value' style options. Now the only option key "target" >> is for uprobe probing. >> >> Signed-off-by: Wang Nan > > looks good. > why use ':' separator? '=' should work as well and will be more > consistent ? Will do. Thank you. -- 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/