Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756032Ab3J1KA5 (ORCPT ); Mon, 28 Oct 2013 06:00:57 -0400 Received: from merlin.infradead.org ([205.233.59.134]:46770 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755993Ab3J1KA4 (ORCPT ); Mon, 28 Oct 2013 06:00:56 -0400 Date: Mon, 28 Oct 2013 11:00:49 +0100 From: Peter Zijlstra To: Will Deacon Cc: Vince Weaver , "linux-kernel@vger.kernel.org" , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: perf: PERF_EVENT_IOC_PERIOD on ARM vs everywhere else Message-ID: <20131028100049.GK19466@laptop.lan> References: <20131028085700.GB20218@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131028085700.GB20218@mudshark.cambridge.arm.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 953 Lines: 18 On Mon, Oct 28, 2013 at 08:57:00AM +0000, Will Deacon wrote: > > Should other architectures be updated to? I just wanted to find out the > > rationale for this before I update the manpage to reflect the difference > > in behaviors between architectures. > > I don't want to be the `oddball' architecture (at least, not more than I am > already :), but I do find it tricky to follow the required semantics of perf > as opposed to `it happens to work this way', especially when so much of it > is buried in the various arch backends. So if somebody using the thing on > ARM has (what looks to me like) a valid issue, then I usually try and fix > it. Hurmph.. at least raise the issue for the other archs. -- 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/