Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2116379ybt; Fri, 3 Jul 2020 00:58:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBNIMVt8LZbcCx58cJvKOcwLO1fD+w7mU9bdPmZHodabkHNkX/4TG0hKc5Zo5aDJedX0ds X-Received: by 2002:a17:906:40d7:: with SMTP id a23mr29682208ejk.421.1593763085394; Fri, 03 Jul 2020 00:58:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593763085; cv=none; d=google.com; s=arc-20160816; b=T9Hg/Q2T2qsB+6U742Gip+nIwZP9C8s2bBgcxa4K9pDqupRNeQnroNi4+Eb20Hooyg q0MWRCxEmxBXhSufzY3ahp0e10MnXU00phLF+pbhI6scLvdY2FSmBlIz6l7P2OBai2RH wqlnnvcU/PtKHTPfrftsnn0b3u37+MZYNOd0bdaR+ZOmumtFNbUK/rCvIbREvix0NH2A KbhuD77d7xCKdubSgBV05ADyOJabc4499zuYoF7CFZT0pVcVp6mXeR0Yrx36vHNVtcQi vXScVHV39cFv+1TWG9MP9MGwUyZKXErvivoatIpLDgR2SW44IijSaUjfNNP463TyFpgk zvoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=JV8hwZUbSwUCZKyuwgk4vToHzbaTKqDD4etCB411ay8=; b=XeHl/wYDdGTOFCOxmLUaRo4zyOHKhdCDzFYt1mZa2egD05OY6D2cjMTj/XwbA8F8T2 Q4jHjNVTpldi/STgZGX3j/5KYuV+18gmiImfXag1fRxMvL++ZWnWNM4Hpn1FxsLrgjmg ARf3rKAvgrn7M/Fy89o34idl8GD+awnRUKwqhDyhwAX1YcRL2xnt9QoNEG7rBiwwJfRF fGONxQTMviMXh77buL8Qup1tl5+Fty7n46Fy1edHsljZLWLOcTSKK5JnPOE6796+J0lv EFPLfMoFFUzKMiQ6FDONbSQgOlyI2Q6ndPiYDcNsmrhcci6uKfBkIpzAQ8eJQqHuuRjf jWbg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=LMbY8QJn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s26si7372984edx.248.2020.07.03.00.57.42; Fri, 03 Jul 2020 00:58:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=LMbY8QJn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726150AbgGCH5Q (ORCPT + 99 others); Fri, 3 Jul 2020 03:57:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39314 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725648AbgGCH5Q (ORCPT ); Fri, 3 Jul 2020 03:57:16 -0400 Received: from merlin.infradead.org (merlin.infradead.org [IPv6:2001:8b0:10b:1231::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2837FC08C5C1; Fri, 3 Jul 2020 00:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.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; bh=JV8hwZUbSwUCZKyuwgk4vToHzbaTKqDD4etCB411ay8=; b=LMbY8QJnU8h++lYC9Ixlw/dQWa 1WEUFZqzw7FpCURd1afG1Z6IWgkxwJebjf4YhQAGW5RoJJPc4LqTTJyzUkwXliHl97EBO2gCoRXIl FA/OuG6pcbp879DUMmHe4MDL26QdmEMvu+pnAuY322ePYwqXIRH5bXR0s4AxkGj4yVu/m0KghQBay owjS3vKCk3yMSTbz0oa2ugslQDKcabPuvXSJEvf7VizjnY8vgIU07t69wd/3clPscDBZ0oIJjwtG2 FSlDfZI1AlrLwieVW8Lz1yKfYcVr+tmt1usfsdKKWL9bMyaZczj7L90f7l39mHhwg87qNdo9QOOil fSxvRchA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=noisy.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1jrGZ3-0000Uj-0I; Fri, 03 Jul 2020 07:56:53 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id D481630377D; Fri, 3 Jul 2020 09:56:46 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id BFD8D203A6153; Fri, 3 Jul 2020 09:56:46 +0200 (CEST) Date: Fri, 3 Jul 2020 09:56:46 +0200 From: Peter Zijlstra To: "Liang, Kan" Cc: Like Xu , Paolo Bonzini , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , ak@linux.intel.com, wei.w.wang@intel.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, "Liang, Kan" Subject: Re: [PATCH v12 00/11] Guest Last Branch Recording Enabling Message-ID: <20200703075646.GJ117543@hirez.programming.kicks-ass.net> References: <20200613080958.132489-1-like.xu@linux.intel.com> <20200702074059.GX4781@hirez.programming.kicks-ass.net> <5d3980e3-1c49-4174-4cdb-f40fc21ee6c1@linux.intel.com> <20200702135842.GR4800@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200702135842.GR4800@hirez.programming.kicks-ass.net> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 02, 2020 at 03:58:42PM +0200, Peter Zijlstra wrote: > On Thu, Jul 02, 2020 at 09:11:06AM -0400, Liang, Kan wrote: > > On 7/2/2020 3:40 AM, Peter Zijlstra wrote: > > > On Sat, Jun 13, 2020 at 04:09:45PM +0800, Like Xu wrote: > > > > Like Xu (10): > > > > perf/x86/core: Refactor hw->idx checks and cleanup > > > > perf/x86/lbr: Add interface to get LBR information > > > > perf/x86: Add constraint to create guest LBR event without hw counter > > > > perf/x86: Keep LBR records unchanged in host context for guest usage > > > > > > > Wei Wang (1): > > > > perf/x86: Fix variable types for LBR registers > > > > > > > arch/x86/events/core.c | 26 +-- > > > > arch/x86/events/intel/core.c | 109 ++++++++----- > > > > arch/x86/events/intel/lbr.c | 51 +++++- > > > > arch/x86/events/perf_event.h | 8 +- > > > > arch/x86/include/asm/perf_event.h | 34 +++- > > > > > > These look good to me; but at the same time Kan is sending me > > > Architectural LBR patches. > > > > > > Kan, if I take these perf patches and stick them in a tip/perf/vlbr > > > topic branch, can you rebase the arch lbr stuff on top, or is there > > > anything in the arch-lbr series that badly conflicts with this work? > > > > > > > Yes, I can rebase the arch lbr patches on top of them. > > Please push the tip/perf/vlbr branch, so I can pull and rebase my patches. > > For now I have: > > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/vlbr > > Once the 0day robot comes back all-green, I'll push it out to > tip/perf/vlbr and merge it into tip/perf/core. tip/perf/vlbr now exists, thanks!