Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757730AbdCUXLc (ORCPT ); Tue, 21 Mar 2017 19:11:32 -0400 Received: from mail.kernel.org ([198.145.29.136]:46738 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757495AbdCUXLb (ORCPT ); Tue, 21 Mar 2017 19:11:31 -0400 Date: Wed, 22 Mar 2017 08:00:18 +0900 From: Masami Hiramatsu To: Arnaldo Carvalho de Melo Cc: Ravi Bangoria , Masami Hiramatsu , alexis.berlemont@gmail.com, linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, mpe@ellerman.id.au, naveen.n.rao@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com Subject: Re: [PATCH 3/5] perf/sdt/x86: Move OP parser to tools/perf/arch/x86/ Message-Id: <20170322080018.7b9a84a9b48ed4c21a94b4bc@kernel.org> In-Reply-To: <20170321141049.GC2531@redhat.com> References: <20161214000732.1710-1-alexis.berlemont@gmail.com> <20170202111143.14319-1-ravi.bangoria@linux.vnet.ibm.com> <20170202111143.14319-4-ravi.bangoria@linux.vnet.ibm.com> <20170207121105.c16c1bded3f24c798eac318a@kernel.org> <58995989.9020202@linux.vnet.ibm.com> <20170321141049.GC2531@redhat.com> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1311 Lines: 33 On Tue, 21 Mar 2017 11:10:49 -0300 Arnaldo Carvalho de Melo wrote: > Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu: > > Thanks Masami for the review. > > > > On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote: > > > On Thu, 2 Feb 2017 16:41:41 +0530 > > > Ravi Bangoria wrote: > > > > > >> SDT marker argument is in N@OP format. N is the size of argument and > > >> OP is the actual assembly operand. OP is arch dependent component and > > >> hence it's parsing logic also should be placed under tools/perf/arch/. > > >> > > > Ok, I have one question. Is there any possibility that N is different > > > size of OP? e.g. 8@dil, in this case we will record whole rdi. > > > is that OK? > > > > By looking at list of markers on my x86 Fedora25 box, yes, it's possible > > for case when register size used in OP is more than size specified by N. > > For example, -4@68(%rbx). But I don't see any argument which specifies > > higher size in N compared to size of register in OP, like you mentioned > > in your example. > > Masami, can I have your Acked-by for 3-5/5 in this series? Arnaldo, as I reviewed, this patch still have some discussion points. Others are good to me. Thanks! -- Masami Hiramatsu