From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754952Ab3EPQ0a (ORCPT ); Thu, 16 May 2013 12:26:30 -0400 Received: from mail-ob0-f170.google.com ([209.85.214.170]:40794 "EHLO mail-ob0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752558Ab3EPQ02 (ORCPT ); Thu, 16 May 2013 12:26:28 -0400 MIME-Version: 1.0 In-Reply-To: <20130516160721.GP4072@tassilo.jf.intel.com> References: <20130503121122.931661809@chello.nl> <20130503121256.083340271@chello.nl> <20130503143507.GP19487@tassilo.jf.intel.com> <20130503170007.GA30733@dyad.programming.kicks-ass.net> <20130515165152.GB13916@laptop.home> <20130516160721.GP4072@tassilo.jf.intel.com> Date: Thu, 16 May 2013 18:26:27 +0200 Message-ID: Subject: Re: [PATCH 1/3] perf, x86: Blacklist all MEM_*_RETIRED events for IVB From: Stephane Eranian To: Andi Kleen Cc: Peter Zijlstra , Ingo Molnar , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 16, 2013 at 6:07 PM, Andi Kleen wrote: >> The difficulty is that we cannot use the shared_regs infrastructure because >> the constraint is quite different. Here we need to say that if a mem event >> uses cnt0 on one thread, then nothing can be using cnt0 on the other thread. >> The current shared_regs infrastructure does not work on the counter level. >> So we need to invent something else. It cannot even be extended. > > Just need a extra reg per counter, that is only triggered with that event. > Yes, it would be per counter and not per-event. But the check has to happen after the assignment and each time we release the counter. > -Andi