From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757126AbbEVPUQ (ORCPT ); Fri, 22 May 2015 11:20:16 -0400 Received: from one.firstfloor.org ([193.170.194.197]:60745 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756620AbbEVPUN (ORCPT ); Fri, 22 May 2015 11:20:13 -0400 Date: Fri, 22 May 2015 17:20:11 +0200 From: Andi Kleen To: Jiri Olsa Cc: Andi Kleen , sukadev@linux.vnet.ibm.com, acme@kernel.org, namhyung@kernel.org, linux-kernel@vger.kernel.org Subject: Re: perf, tools: Event files for Intel x86 Message-ID: <20150522152011.GG19417@two.firstfloor.org> References: <1432181493-18743-1-git-send-email-andi@firstfloor.org> <20150522150256.GC16473@krava.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150522150256.GC16473@krava.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Currently only core events are included, not uncore. > > hum, not sure how you guys want to handle this, but it'd be nice > to have all the bits in one place.. Could one of you guys please > arrange branch with all this? I would suggest to handle the code together in a single branch. And then handle the events separately per architecture, just as pull requests without posting. I doubt anyone on linux-kernel would be happy about getting that large files in mail; in fact the list software may not allow it. -Andi -- ak@linux.intel.com -- Speaking for myself only.