Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp8103933ybi; Thu, 6 Jun 2019 06:48:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqxCaNsnXadIOCYYs2PWGUWDh+g0W5dovu69S+UUTDmZQaYd5KnyY7Etn7OSsesNBPUGWovo X-Received: by 2002:a17:902:54d:: with SMTP id 71mr49238945plf.140.1559828920745; Thu, 06 Jun 2019 06:48:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559828920; cv=none; d=google.com; s=arc-20160816; b=lK4NAyPVSrRQgAzMz6TATCBgYdETtK3mJpigus8t73ORWjj33PWPYa5G9iqORwLO/a 6jOf49H5nbVlGRacvrG6RwKzTjGq9QpvD4XL3jtyhseN6KwgbPAwrdlsCenelVkMn0hI zT8FFCb+rbv2W84TL2vLuZdP3Od8b9ATXBzLkK19yJXXdAKl9Pl/GBhT+Ilaktr5P030 6L1cRIMqjb2O4sPN5kazVwlbmvM8diZ0WUAGJ7Iykm8iVZFaHTp4R2kL8G41XaVBGzSF OpA4Apr7cXDJfSl6QdUUPCNSHkL9OMwvvlug0ami2ALoPB40d0D/HJiBIFHpK+kFr/SK IjUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature; bh=sxuZRg/a5BwwLpOXc2E8P4g4IXtD5jAKIRcm5GraeZs=; b=R9yYiUDi0DEkm2PClyQPpDZu5UtSAb3+KcxC+VqSsg2qQiwKnoGob8bJvRYJWLgRny +xeM2J6zO+f9G6ka8ywGNwwWYNtmUrY5401b1LaZsBDCA/bn4weYKI/sESCLMmTP1kmI VqRUTnsSsEaoRA+IqSdvaUuvBezmKZsOaKEp1M6SxQgOsADSI7sDJ5bXFmb3bgbp+znm uhYA7y4VoISe/hRHnpiV1o+2uH5F83zBB6+VXd7h32nFRHjQaU5VbaX4/L/Bp0qsyJ9D 1KD3rgcKIhRW1067atnjQOJPH0QSBeVno1zPlPWkXDEIB4mWdATNYqlu9401qvDScRn+ 4Z1A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=XHOrwfS8; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b2si1809805pls.93.2019.06.06.06.48.24; Thu, 06 Jun 2019 06:48:40 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=XHOrwfS8; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728630AbfFFNqa (ORCPT + 99 others); Thu, 6 Jun 2019 09:46:30 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:33288 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726877AbfFFNqa (ORCPT ); Thu, 6 Jun 2019 09:46:30 -0400 Received: by mail-qt1-f194.google.com with SMTP id 14so2717331qtf.0; Thu, 06 Jun 2019 06:46:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=sxuZRg/a5BwwLpOXc2E8P4g4IXtD5jAKIRcm5GraeZs=; b=XHOrwfS8/mtrMMyB0x5R2qAgNUAIbmokPuEjYslAfmR42hmTwX6mUmvqN0qJVubtIA apBbNQEYjXPml15lz6BHEJTV10xXUF5a6sDyMzyaiyne5WyQLcBKqZPkonlIeHJsVGeM m7wlYApzbK9DFyYGaWuyjgPUexcb9gM9Z78ysaRPD5M+FgS52C8hZJ85gec5f0OUj1Q1 IODc0tO8cks0OwbkxIrpk1JLV8DGd0RTdzDZW7beSOlIe6BEMRk9LukdwPPTrpWmbjVh XKBQfQNgo+jLan7eW+FMPE3CY69AggrgnhF2KWAH2HBjK7a15UvDrlnFSJoQNGGeekgW RdEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=sxuZRg/a5BwwLpOXc2E8P4g4IXtD5jAKIRcm5GraeZs=; b=oelqLTW1K7m53dxWmCWg1ZGiFuJ11gOzPgnirEc7Aw7yacMZ7z+JpDr82iAVum/i/B RWqv/7MNKk4SJzJTM61manXDTSEpjPTFepGAD85KaxWzfQ890X9T5EYwmv0Yk02GAoHA KwzaWEhRF8//CegcFoYH2oLUXkYdOAbbKbUREfezGJ8yMjNbCXP2S53aCymH1/7/GYnV M0QLC6ohokP47Z5p+CRVdUaTI8oYuLrYFb7pUcPDL1auQyeHkriz/MOwGYPj4JWjRnkd pWYlA1h+Yf+9iNrz/CyXpCqc3oPVTeEFekovRjuda8fJQ682keN1ia3F9mccmY5SeR1b O0RQ== X-Gm-Message-State: APjAAAXNjo7Kdvq3B8YH2Z7W8iXNc5hibQFfCAokE53vc7yMdrtzNtXj oefYbCwIvmJRKp3PzR8rJDI= X-Received: by 2002:a0c:99d8:: with SMTP id y24mr38959520qve.74.1559828789107; Thu, 06 Jun 2019 06:46:29 -0700 (PDT) Received: from quaco.ghostprotocols.net ([177.195.208.82]) by smtp.gmail.com with ESMTPSA id d38sm1344329qtb.95.2019.06.06.06.46.27 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 06 Jun 2019 06:46:27 -0700 (PDT) From: Arnaldo Carvalho de Melo X-Google-Original-From: Arnaldo Carvalho de Melo Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id 41B7441149; Thu, 6 Jun 2019 10:46:24 -0300 (-03) Date: Thu, 6 Jun 2019 10:46:24 -0300 To: Leo Yan Cc: Alexander Shishkin , Jiri Olsa , Namhyung Kim , Alexei Starovoitov , Daniel Borkmann , Martin KaFai Lau , Song Liu , Yonghong Song , Adrian Hunter , Mathieu Poirier , Mike Leach , Suzuki K Poulose , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org Subject: Re: [PATCH v2 3/4] perf augmented_raw_syscalls: Support arm64 raw syscalls Message-ID: <20190606134624.GD30166@kernel.org> References: <20190606094845.4800-1-leo.yan@linaro.org> <20190606094845.4800-4-leo.yan@linaro.org> <20190606133838.GC30166@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190606133838.GC30166@kernel.org> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Thu, Jun 06, 2019 at 10:38:38AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Thu, Jun 06, 2019 at 05:48:44PM +0800, Leo Yan escreveu: > > This patch adds support for arm64 raw syscall numbers so that we can use > > it on arm64 platform. > > > > After applied this patch, we need to specify macro -D__aarch64__ or > > -D__x86_64__ in compilation option so Clang can use the corresponding > > syscall numbers for arm64 or x86_64 respectively, other architectures > > will report failure when compilation. > > So, please check what I have in my perf/core branch, I've completely > removed arch specific stuff from augmented_raw_syscalls.c. > > What is done now is use a map to specify what to copy, that same map > that is used to state which syscalls should be traced. > > It uses that tools/perf/arch/arm64/entry/syscalls/mksyscalltbl to figure > out the mapping of syscall names to ids, just like is done for x86_64 > and other arches, falling back to audit-libs when that syscalltbl thing > is not present. Also added: Fixes: ac96287cae08 ("perf trace: Allow specifying a set of events to add in perfconfig") For the stable@kernel.org folks to automagically pick this. - Arnaldo