Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Pei <cp0613@linux.alibaba.com>
To: adrian.hunter@intel.com
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
	guoren@kernel.org, irogers@google.com, james.clark@linaro.org,
	john.g.garry@oracle.com, jolsa@kernel.org, leo.yan@linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-riscv@lists.infradead.org, mark.rutland@arm.com,
	mike.leach@arm.com, mingo@redhat.com, namhyung@kernel.org,
	palmer@dabbelt.com, peterz@infradead.org, pjw@kernel.org,
	will@kernel.org
Subject: Re: [PATCH v2 2/2] perf tsc: Declare TSC support from the build system
Date: Fri,  9 Oct 2026 10:24:22 +0800	[thread overview]
Message-ID: <20261009022424.2604-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <66136aa8-adbe-4fdf-9b7c-d44ea0e5cf1e@intel.com>

Hi Adrian,

On Tue, 6 Oct 2026, Adrian Hunter wrote:
> Perhaps with #include <tools/config.h> the following is tidier:
>
> 	if (!IS_BUILTIN(HAVE_RDTSC)) {
> 		pr_debug("Test not supported on this architecture\n");
> 		return TEST_SKIP;
> 	}

Thanks for the review.  I'll change it as suggested and post v3.

Best regards,
Pei

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2026-10-09  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  3:41 [PATCH v2 0/2] perf riscv: Implement rdtsc() Chen Pei
2026-09-29  3:41 ` [PATCH v2 1/2] " Chen Pei
2026-10-07 15:28   ` Paul Walmsley
2026-09-29  3:41 ` [PATCH v2 2/2] perf tsc: Declare TSC support from the build system Chen Pei
2026-09-29  9:49   ` Leo Yan
2026-10-06 13:16   ` Adrian Hunter
2026-10-07 15:31     ` Paul Walmsley
2026-10-09  2:24     ` Chen Pei [this message]

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=20261009022424.2604-1-cp0613@linux.alibaba.com \
    --to=cp0613@linux.alibaba.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=guoren@kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.leach@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=will@kernel.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