linux-kernel - Re: [PATCH v3 5/9] perf, x86: large PEBS interrupt threshold

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 23 Jul 2014 08:59:03 +0800
From:	"Yan, Zheng" <zheng.z.yan@...el.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	mingo@...nel.org, acme@...radead.org, eranian@...gle.com
Subject: Re: [PATCH v3 5/9] perf, x86: large PEBS interrupt threshold

On 07/23/2014 12:16 AM, Andi Kleen wrote:
>> +	/*
>> +	 * When the event is constrained enough we can use a larger
>> +	 * threshold and run the event with less frequent PMI.
>> +	 */
>> +	if (0 && /* disable this temporarily */
> 
> Where in the patchkit does it get reenabled?

enabled by patch 7
> 
> -Andi
> 
>> +	    (hwc->flags & PERF_X86_EVENT_AUTO_RELOAD) &&
>> +	    !(event->attr.sample_type & ~PEBS_FREERUNNING_FLAGS)) {
>> +		threshold = ds->pebs_absolute_maximum -
>> +			x86_pmu.max_pebs_events * x86_pmu.pebs_record_size;
>> +	} else {
>> +		threshold = ds->pebs_buffer_base + x86_pmu.pebs_record_size;
>> +	}
>> +	if (first_pebs || ds->pebs_interrupt_threshold > threshold)
>> +		ds->pebs_interrupt_threshold = threshold;

--
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/