• Peter Zijlstra's avatar
    perf/x86/intel: Make WARN()ings consistent · 17186ccd
    Peter Zijlstra authored
    The intel_commit_scheduling() callback is pointlessly different from
    the start and stop scheduling callback.
    
    Furthermore, the constraint should never be NULL, so remove that test.
    
    Even though we'll never get called (because we NULL the callbacks)
    when !is_ht_workaround_enabled() put that test in.
    
    Collapse the (pointless) WARN_ON_ONCE() and bail on !cpuc->excl_cntrs --
    this is doubly pointless, because its the same condition as
    is_ht_workaround_enabled() which was already pointless because the
    whole method won't ever be called.
    
    Furthremore, make all the !excl_cntrs test WARN_ON_ONCE(); they're all
    pointless, because the above, either the function
    ({get,put}_excl_constraint) are already predicated on it existing or
    the is_ht_workaround_enabled() thing is the same test.
    Signed-off-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Vince Weaver <vincent.weaver@maine.edu>
    Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
    17186ccd
perf_event_intel.c 93.2 KB