Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp105204imm; Wed, 3 Oct 2018 12:41:43 -0700 (PDT) X-Google-Smtp-Source: ACcGV60udQ7Gkwk3VTs+YmSvqm4xpCES0Wrcvjq0iXpuv3dMhfKy4WxDV4b3qEtGZmSod0BoYDQR X-Received: by 2002:a63:9507:: with SMTP id p7-v6mr2700289pgd.449.1538595702997; Wed, 03 Oct 2018 12:41:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538595702; cv=none; d=google.com; s=arc-20160816; b=k/EzY8jc3V3oYXUMSJAtOO2O+iB++jQsONSaAdpcAg5/bo7cPQyzr0WMg9gNv4YdaA LjECCd4ysjJwYjmk4pNzfEMSJowkcMzocffi8EdbANJZA43r88vbDyjsBMlAbDrUW28r 8CAYoTinLDQmYgmnCRxLPllEp/G6m+ZAlRR9TIMsRpX6tySJ/NHFI5TaS0YdJAuqqr2x Vwql2DBzaC0SKKTjIzx/N6jqXOTxB4Kibx4SmnWUJUWN2AUX/glwyHvM4Rg/ZRbm0lBU jbDwtgyQixtratZWfV0vAWCVUWR3xmTLaBHMuRJ72a8SLhWrSjSi+RgJRsAnrSc6spmD WVFQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=7lzDSuSJbRrFRKi5f4IynybUq/msSz0hpUXleQ2NcEM=; b=QQHDZuUWKo7rMYyEc73YNVSaunMWG7l4u9+fFLUWVeKVVCuc4uaJXSC5Qfna3ejhFX 9a/ezgL5lbg1m+bRW0BUSykFa6W9cBj3EOB2gQ8BqOpLioTiVy6RVV3sdiXTtxWCS1XL 3mbtH8XwgBtHO/E/GMlAnjDNSPzDyunppgIZTE0T/BoSYDCSTwuxOvF7Dr2STZVkwnHy tvvBknDrxEM2ArvlKcrTc+i51nLHgj/LFE9PQhwAUtte1Phptl6z2YZo7sqxxLXagEaY ztfBRRUisZ7YaiT6Sd3je09HDfKGUS5AkB2bgZT+H7bD+GOIfnpDRWySodtwKSGC+8p0 8Ppw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l9-v6si2566690pfi.179.2018.10.03.12.41.26; Wed, 03 Oct 2018 12:41:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727269AbeJDCbG (ORCPT + 99 others); Wed, 3 Oct 2018 22:31:06 -0400 Received: from mga06.intel.com ([134.134.136.31]:47977 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726969AbeJDCbF (ORCPT ); Wed, 3 Oct 2018 22:31:05 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Oct 2018 12:41:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,337,1534834800"; d="scan'208";a="94376477" Received: from rchatre-mobl.amr.corp.intel.com (HELO [10.24.14.135]) ([10.24.14.135]) by fmsmga004.fm.intel.com with ESMTP; 03 Oct 2018 12:41:18 -0700 Subject: Re: [PATCH V5 0/6] perf and x86/intel_rdt: Fix lack of coordination with perf To: Thomas Gleixner Cc: Peter Zijlstra , fenghua.yu@intel.com, tony.luck@intel.com, mingo@redhat.com, acme@kernel.org, gavin.hindman@intel.com, jithu.joseph@intel.com, dave.hansen@intel.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org References: <20180920141150.GY24124@hirez.programming.kicks-ass.net> <77383a1e-f343-7529-24cf-874f0999507d@intel.com> <20180928065830.GE3439@hirez.programming.kicks-ass.net> <42c2b375-dbb9-11a3-8e2f-bec744e73b10@intel.com> From: Reinette Chatre Message-ID: <0497d8a4-2dc8-3dca-28bd-58c5f6489218@intel.com> Date: Wed, 3 Oct 2018 12:41:17 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, On 9/29/2018 10:56 AM, Thomas Gleixner wrote: > Reinette, > > On Sat, 29 Sep 2018, Reinette Chatre wrote: >> I interpreted Thomas and Peter's responses to mean that there are no >> objections for this to be included in v4.19 as a fix. >> >> If I understand the tip branches correctly the core patch seems to be >> headed to v4.19 while the rest (excluding the final patch >> "x86/intel_rdt: Re-enable pseudo-lock measurements") are headed to v4.20. >> >> Have you decided against including this into v4.19 or did I >> misunderstand the responses and/or branches? > > I did not decide anything yet. It's not going into -rc6 as it's not yet > through next and the other standard testing. > > I'm also looking at the other set of RDT fixes, which obviously want to go > as well. So not sure how to deal with all of that. > When you do deal with this series could you please also include the final patch ("x86/intel_rdt: Re-enable pseudo-lock measurements")? I noticed that patches 1/6 to 5/6 have been merged into x86/cache in tip.git and then some other work on top of it. It is not clear to me why 6/6 was omitted and this fix does require it. Thank you very much Reinette