Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752148Ab0KZLZ4 (ORCPT ); Fri, 26 Nov 2010 06:25:56 -0500 Received: from smtp-out.google.com ([74.125.121.35]:12798 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750880Ab0KZLZz (ORCPT ); Fri, 26 Nov 2010 06:25:55 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sNlipDGalH+J/V1J5UNWVi5CduwHxiDDpf7ahX3TJC+pIfYD7VBdXAyaO5/5UQqzJf b0b0vXVVRbVuEYa7OBUQ== MIME-Version: 1.0 In-Reply-To: <1290770652.2145.128.camel@laptop> References: <1290340877.2245.124.camel@localhost> <1290770652.2145.128.camel@laptop> Date: Fri, 26 Nov 2010 12:25:51 +0100 Message-ID: Subject: Re: [RFC PATCH 2/3 v2] perf: Implement Nehalem uncore pmu From: Stephane Eranian To: Peter Zijlstra Cc: Lin Ming , Lin Ming , Ingo Molnar , Andi Kleen , lkml , Frederic Weisbecker , Arjan van de Ven Content-Type: text/plain; charset=UTF-8 X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1020 Lines: 22 On Fri, Nov 26, 2010 at 12:24 PM, Peter Zijlstra wrote: > On Fri, 2010-11-26 at 09:18 +0100, Stephane Eranian wrote: > >> In the perf_event model, given that any one of the 4 cores can be used >> to program uncore events, you have no choice but to broadcast to all >> 4 cores. Each has to demultiplex and figure out which of its counters >> have overflowed. > > Not really, you can redirect all these events to the first online cpu of > the node. > > You can re-write event->cpu in pmu::event_init(), and register cpu > hotplug notifiers to migrate the state around. > I am sure you could. But then the user thinks the event is controlled from CPUx when it's actually from CPUz. I am sure it can work but that's confusing, especially interrupt-wise. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/