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
| ||
|
Message-ID: <20140722161617.GQ18735@two.firstfloor.org> Date: Tue, 22 Jul 2014 18:16:18 +0200 From: Andi Kleen <andi@...stfloor.org> To: "Yan, Zheng" <zheng.z.yan@...el.com> Cc: linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl, mingo@...nel.org, acme@...radead.org, eranian@...gle.com, andi@...stfloor.org Subject: Re: [PATCH v3 5/9] perf, x86: large PEBS interrupt threshold > + /* > + * 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? -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/
Powered by blists - more mailing lists