From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,T_DKIM_INVALID, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4BB30C43142 for ; Thu, 2 Aug 2018 20:28:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E640221566 for ; Thu, 2 Aug 2018 20:28:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="OLTj+P2g" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E640221566 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731578AbeHBWVJ (ORCPT ); Thu, 2 Aug 2018 18:21:09 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:52784 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727302AbeHBWVJ (ORCPT ); Thu, 2 Aug 2018 18:21:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=OopUoc9Oo3QAeBLMiNvjTdoE6BnD12rp59cBD1G4PIA=; b=OLTj+P2gkf43DP/fhCwMN90sU 71WAmb1q7m3lMADGVBsoUBDdEZHiFxc7XnlW7q1vpx9lY7O2TyLle+crkaF2l7JFYoxxyZrTDPBWt TVYe2AfaTDNGriM2bqqP4P5BqaekQ3fXsQ9RWm6cjocuMJM/aIacYNDPo/VwLupvCZ81aMnJ4UEIU FFF3pKbHBcd/WadHTlyGG7Fxsr3JIVFyOcDx8sxlJRqwoYhe24/cwqnYXGSwe2HKMJ/UmuRN26wDd xWlfvSNErF5J6HInwFFVYasOcd9I2eV8bGOQokJYiBibtfXPVYx7p+xuEkqvw9erHGOSJL17WMACB 1rbH9PimA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1flJyD-0000kJ-Va; Thu, 02 Aug 2018 20:13:14 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 5297F20268267; Thu, 2 Aug 2018 22:13:12 +0200 (CEST) Date: Thu, 2 Aug 2018 22:13:12 +0200 From: Peter Zijlstra To: Dave Hansen Cc: Reinette Chatre , tglx@linutronix.de, mingo@redhat.com, fenghua.yu@intel.com, tony.luck@intel.com, vikas.shivappa@linux.intel.com, gavin.hindman@intel.com, jithu.joseph@intel.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] x86/intel_rdt and perf/x86: Fix lack of coordination with perf Message-ID: <20180802201312.GS2494@hirez.programming.kicks-ass.net> References: <20180802123923.GJ2530@hirez.programming.kicks-ass.net> <1af731f8-b5d3-5aca-af02-575802a961b9@intel.com> <20180802161823.GJ2458@hirez.programming.kicks-ass.net> <20180802173727.GP2494@hirez.programming.kicks-ass.net> <653e874f-5e77-a9b5-996a-ed9daa3c6d43@intel.com> <20180802195410.GR2494@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 02, 2018 at 01:06:19PM -0700, Dave Hansen wrote: > On 08/02/2018 12:54 PM, Peter Zijlstra wrote: > >> I totally understand not wanting to fill the tree with code hijacking > >> the raw PMU. Is your reaction to this really around not wanting to > >> start down the slippery slope that ends up with lots of raw PMU "owners"? > > That and the fact that multiple owner directly contradicts what perf set > > out to do, provide resource arbitration for the PMU. > > > > Not being able to use both perf and this resctl thing at the same time > > is utter crap. You will not get special dispensation. > > Is there something we could do in the middle, like have perf itself be > in charge of doing all the programming, but the psuedo-locking could > still _read_ the counters? perf has all of that.