From: Eric Cheng <eric.cheng.linux@gmail.com>
To: Shenlin Liang <liangshenlin@eswincomputing.com>,
anup@brainfault.org, atishp@atishpatra.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/2] RISCV: KVM: add tracepoints for entry and exit events
Date: Wed, 10 Apr 2024 15:12:52 +0800 [thread overview]
Message-ID: <40a8d9d3-20a8-44e8-96d2-0dcd8627cfc8@gmail.com> (raw)
In-Reply-To: <20240328031220.1287-2-liangshenlin@eswincomputing.com>
On 3/28/2024 11:12 AM, Shenlin Liang wrote:
> Like other architectures, RISCV KVM also needs to add these event
> tracepoints to count the number of times kvm guest entry/exit.
>
> Signed-off-by: Shenlin Liang <liangshenlin@eswincomputing.com>
> ---
> arch/riscv/kvm/trace_riscv.h | 60 ++++++++++++++++++++++++++++++++++++
Conventionally, it should be named to trace.h, especially if only one. Refer to
other arch's.
next prev parent reply other threads:[~2024-04-10 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 3:12 [PATCH 0/2] perf kvm: Add kvm stat support on riscv Shenlin Liang
2024-03-28 3:12 ` [PATCH 1/2] RISCV: KVM: add tracepoints for entry and exit events Shenlin Liang
2024-04-08 12:07 ` Anup Patel
2024-04-11 7:24 ` Shenlin Liang
2024-04-10 7:12 ` Eric Cheng [this message]
2024-04-11 7:24 ` Shenlin Liang
2024-03-28 3:12 ` [PATCH 2/2] perf kvm/riscv: Port perf kvm stat to RISC-V Shenlin Liang
2024-04-07 2:31 ` [PATCH 0/2] perf kvm: Add kvm stat support on riscv Shenlin Liang
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=40a8d9d3-20a8-44e8-96d2-0dcd8627cfc8@gmail.com \
--to=eric.cheng.linux@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=liangshenlin@eswincomputing.com \
--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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--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).