Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp108382imm; Wed, 3 Oct 2018 12:45:53 -0700 (PDT) X-Google-Smtp-Source: ACcGV61H3P6JIcXt3m6pgYjgoUOssTkRxBOIEWD3+Wsg4QLYDvGTRXc7trGMcepXBrti2sZ4Oc/l X-Received: by 2002:a17:902:4381:: with SMTP id j1-v6mr3110982pld.59.1538595953137; Wed, 03 Oct 2018 12:45:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538595953; cv=none; d=google.com; s=arc-20160816; b=RyR5R5qasfcINYNaVWwDWl/x4SXAtg58qWw6oQfAvhZgQNcY3UAXuNMcAbQ1k05PZD RJ8xGDbnKDBHafdlJq4SALnhNliY8TYPLyZ0CNgMUn3x3wz3FjCMeHqstDrv3RiRxCaJ J/PGRPwP24giyljEIEmq3dVudoGSQdIF80H/DWmFy8edi+azfyGEiUeGZHa1P9MWQTrA aZfiUnJ6LKkADJvZP/6kAL7G61n2NDQNzHspFdOm4zI6xhGx83zz3tKke7joCESJNBbc XmTG8cGw9fdABDJKUJ2CI+sJ7v+mfrl+AGJWSC4Uxj9Jei6t17UeKOvg5csEphwpUkQq +2Cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=UlGl2X2V7eKGkYVj9TvPmN6YGLP5fVD2hld+5eJfl1s=; b=gR6WDvx4yUpF74qV5Cb3SeCeTHt02liB8oHrp7fOqYM5RPO234wztMsXNipY4BKbe4 U7+Ctti3BGsdAZh3bjWT5zpojDLEi68gwTtn4QeMPE4Hoe79F5MX3PkFD7XHHoMY/AYV 0Tmg+A9WRw54VC0Cr/OgsQ2HGvx9HJ5kyW/Nnl5k+McvJPk4qn3Oyp4xG+0Gtx0umy83 /tVCrWQ1lxDvf7HRLx4v6PdSFL7UYzcFB3ly5tJ+StygL7xpbWVsKIH8T7ibHw8bK/b4 xLAazdpa6T2v79jlWpS7WXH9vwnDOgb1WDuHY9sm8rvTNaM4hmThoELgyOEmlN1w3dJK Nd2A== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d33-v6si2481053pla.292.2018.10.03.12.45.37; Wed, 03 Oct 2018 12:45:53 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727164AbeJDCfJ (ORCPT + 99 others); Wed, 3 Oct 2018 22:35:09 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34649 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726971AbeJDCfJ (ORCPT ); Wed, 3 Oct 2018 22:35:09 -0400 Received: from tmo-108-185.customers.d1-online.com ([80.187.108.185] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1g7n4x-0004BX-1I; Wed, 03 Oct 2018 21:45:03 +0200 Date: Wed, 3 Oct 2018 21:45:01 +0200 (CEST) From: Thomas Gleixner To: Reinette Chatre 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 Subject: Re: [PATCH V5 0/6] perf and x86/intel_rdt: Fix lack of coordination with perf In-Reply-To: <0497d8a4-2dc8-3dca-28bd-58c5f6489218@intel.com> Message-ID: 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> <0497d8a4-2dc8-3dca-28bd-58c5f6489218@intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Oct 2018, Reinette Chatre wrote: > 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. Hmm. That was not intentional. /me goes to rumage around. Thanks, tglx