On Thu, Jun 5, 2014 at 10:32 AM, Matt Fleming <m...@console-pimps.org> wrote: > On 4 June 2014 22:34, Stephane Eranian <eran...@google.com> wrote: >> From: Maria Dimakopoulou <maria.n.dimakopou...@gmail.com> >> >> This patch adds a sysfs entry: >> >> /sys/devices/cpu/ht_bug_workaround >> >> to activate/deactivate the PMU HT bug workaround. >> >> To activate (activated by default): >> # echo 1 > /sys/devices/cpu/ht_bug_workaround >> >> To deactivate: >> # echo 0 > /sys/devices/cpu/ht_bug_workaround > > If your hardware contains this erratum, why would you ever want to > disable the workaround? Providing the user with the option of turning > this off seems like a bad idea. > > I suspect that users will rarely know whether they can legitimately > disable this.
If you know what you are doing (poweruser), then there are measurements which works fine with the HT erratum. This is why we have the option. For instance if you only measure events 4x4 in system-wide mode and you know which counters these event are going to use, you don't need the workaround. For instance: # perf stat -a -e r81d0,r01d1,r08d0,r20d1 sleep 5 Works well if you have a uniform workload across all CPUs. All those events leak, but the leaks balance themselves and you get the correct counts in the end. The advantage is that you don't have to multiplex. With the workaround enable, this would multiplex a lot. But as I said, this is for experts only. Another reason is for systems with HT disabled. It turned out to be very difficult to determine at kernel BOOT TIME if HT was enabled or not. Note what I said: ENABLED and not SUPPORTED. The latter is easy to detect. The former needs some model specific code which is quite complicated. I wish the kernel had this capability abstracted somehow. Consequently, the workaround is always enabled. When HT is disabled, there won't be multiplexing because there will never be conflict, but you pay a little price for accessing the extra data state. An init script could well detect HT is off and thus disable the workaround altogether. Those are the two main reasons for this control in sysfs. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
