linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <siyanteng@loongson.cn>
To: acme@kernel.org
Cc: Yanteng Si <siyanteng@loongson.cn>,
	mingo@redhat.com, peterz@infradead.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	namhyung@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	chenhuacai@kernel.org, linux-perf-users@vger.kernel.org,
	loongson-kernel@lists.loongnix.cn, loongarch@lists.linux.dev
Subject: [PATCH v1 0/2] tools/perf: Add loongarch cpuinfo and fix build warning
Date: Tue, 22 Aug 2023 17:32:05 +0800	[thread overview]
Message-ID: <cover.1692694595.git.siyanteng@loongson.cn> (raw)

* LoongArch and riscv don't have tools/arch/xxxxx/include/uapi/asm/mman.h, 
  let's modify the detection rules.
* Allow to use cpuinfo on loongarch.

Yanteng Si (2):
  perf/trace: Fix mmap_flags for archs use generic mman.h
  perf/tools: Allow to use cpuinfo on loongarch

 tools/perf/trace/beauty/mmap_flags.sh | 2 +-
 tools/perf/util/header.c              | 2 ++
 tools/perf/util/svghelper.c           | 7 ++++++-
 3 files changed, 9 insertions(+), 2 deletions(-)

-- 
2.31.4


             reply	other threads:[~2023-08-22  9:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  9:32 Yanteng Si [this message]
2023-08-22  9:32 ` [PATCH v1 1/2] perf/trace: Fix mmap_flags for archs use generic mman.h Yanteng Si
2023-08-22 18:02   ` Arnaldo Carvalho de Melo
2023-08-23  7:11     ` Yanteng Si
2023-08-23 11:36       ` Arnaldo Carvalho de Melo
2023-08-24  2:22         ` Yanteng Si
2023-08-24 13:33           ` Arnaldo Carvalho de Melo
2023-08-22  9:32 ` [PATCH v1 2/2] perf/tools: Allow to use cpuinfo on loongarch Yanteng Si
2023-08-22 17:50   ` Arnaldo Carvalho de Melo
2023-08-23  7:11     ` Yanteng Si
2023-08-22 15:10 ` [PATCH v1 0/2] tools/perf: Add loongarch cpuinfo and fix build warning Huacai Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1692694595.git.siyanteng@loongson.cn \
    --to=siyanteng@loongson.cn \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=chenhuacai@kernel.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=loongson-kernel@lists.loongnix.cn \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).