Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756856Ab1EXRms (ORCPT ); Tue, 24 May 2011 13:42:48 -0400 Received: from aspirin.dii.utk.edu ([160.36.0.81]:38879 "EHLO aspirin.dii.utk.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754507Ab1EXRmr (ORCPT ); Tue, 24 May 2011 13:42:47 -0400 Date: Tue, 24 May 2011 13:42:35 -0400 (EDT) From: Vince Weaver To: Peter Zijlstra cc: linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org, acme@redhat.com Subject: Re: perf: regression -- missing /sys/devices/system/cpu/perf_events In-Reply-To: <1306246306.18455.36.camel@twins> Message-ID: References: <1306246306.18455.36.camel@twins> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 611 Lines: 17 On Tue, 24 May 2011, Peter Zijlstra wrote: > A much more reliable way is simply doing the syscall and seeing what > happens. But if you want to poke around in sysfs, /sys/bus/event_source/ > is the new location. It's been suggested that they can look for the existence of: /proc/sys/kernel/perf_event_paranoid is that something not likely to go away? Vince -- 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/