linux-kernel - Re: [RFC PATCH 3/3] perf tool: Allow wildcard in PMU name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5057E660.3040308@intel.com>
Date:	Tue, 18 Sep 2012 11:11:28 +0800
From:	"Yan, Zheng" <zheng.z.yan@...el.com>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
CC:	Jiri Olsa <jolsa@...hat.com>, eranian@...gle.com,
	a.p.zijlstra@...llo.nl, mingo@...e.hu, andi@...stfloor.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 3/3] perf tool: Allow wildcard in PMU name

On 09/17/2012 11:36 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 11, 2012 at 04:27:17PM +0200, Jiri Olsa escreveu:
>> On Mon, Sep 10, 2012 at 03:53:51PM +0800, Yan, Zheng wrote:
>>
>> Would it be possible to have all '*add_event' more obvious for usage.
>> Also following code is duplicated after each call of __add_event:
>>
>>       evsel = __add_event(idx, &attr, pmu_event_name(head_config),
>>                           pmu->cpus);
>>       if (!evsel) {
>>               *idx = orig_idx;
>>               free_event_list(list);
>>               return -ENOMEM;
>>       }
>>       list_add_tail(&evsel->node, list);
> 
> Any update here? Yan, did you look at folding Jiri's patch? I'm merging
> the first bit, the kernel part, that was Acked by Ingo and Peter,
> waiting on this part, looking at 2/3 now
> 

Hi,

This patch still need some improvement, I don't expect it to get merged.
Please merged the patch 1 and patch 2 first. I will send a new one soon.

Regards
Yan, Zheng

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