From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: lirongqing <lirongqing@baidu.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Leo Yan <leo.yan@linux.dev>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf kvm: Fix arm64 VM-exit duration accounting
Date: Wed, 4 Nov 2026 18:19:25 -0300 [thread overview]
Message-ID: <auuhXYYpDW3UZn90@phoenix2> (raw)
In-Reply-To: <20261104111751.GG9176@e132581.arm.com>
On Wed, Nov 04, 2026 at 11:17:51AM +0000, Leo Yan wrote:
> On Sat, Oct 31, 2026 at 08:01:23PM +0800, lirongqing wrote:
> > From: Li RongQing <lirongqing@baidu.com>
> >
> > Use kvm_exit as the start event and the following kvm_entry as the
> > end event for arm64 VM-exit statistics. Keep decoding ret and esr_ec
> > from the exit sample.
> >
> > Before this change, arm64 measured guest runtime as VM-exit time.
> >
> > Fixes: 1218838d68f5 ("perf kvm: Add kvm-stat for arm64")
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
>
> Thanks for the fix!
>
> Reviewed-by: Leo Yan <leo.yan@arm.com>
>
> Since arm64 requires the exit reason, we cannot directly use the common
> exit_event_begin()/exit_event_end() callbacks as other archs do.
Thanks, applied for v7.4.
- Arnaldo
prev parent reply other threads:[~2026-11-04 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 12:01 [PATCH] perf kvm: Fix arm64 VM-exit duration accounting lirongqing
2026-10-31 12:05 ` sashiko-bot
2026-11-04 11:17 ` Leo Yan
2026-11-04 21:19 ` Arnaldo Carvalho de Melo [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=auuhXYYpDW3UZn90@phoenix2 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=leo.yan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=senozhatsky@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.