From: Andi Kleen <ak@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Leo Yan <leo.yan@linaro.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH 6/6] perf intel-pt: Add guest_code support
Date: Fri, 13 May 2022 11:13:49 -0700 [thread overview]
Message-ID: <871qwxgv1e.fsf@linux.intel.com> (raw)
In-Reply-To: <df56f04b-cb25-5a47-ffef-b2e2ee0f6b74@intel.com> (Adrian Hunter's message of "Fri, 13 May 2022 18:14:49 +0300")
Adrian Hunter <adrian.hunter@intel.com> writes:
>>
>> I'm still not fully sure how it exactly finds the code on the host,
>> how is the code transferred?
>
> I don't know. From a quick look at the code in
> tools/testing/selftests/kvm/lib/kvm_util.c it seems to be using
> KVM_SET_USER_MEMORY_REGION IOCTL.
Okay so it assumes that the pages with code on the guest are still intact: that is
you cannot quit the traced program, or at least not do something that would
fill it with other data?. Is that correct?
It sounds like with that restriction it's more useful for kernel traces.
-Andi
next prev parent reply other threads:[~2022-05-13 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:02 [PATCH 0/6] perf intel-pt: Add support for tracing KVM test programs Adrian Hunter
2022-05-13 9:02 ` [PATCH 1/6] perf tools: Add machine to machines back pointer Adrian Hunter
2022-05-13 9:02 ` [PATCH 2/6] perf tools: Factor out thread__set_guest_comm() Adrian Hunter
2022-05-13 9:02 ` [PATCH 3/6] perf tools: Add guest_code support Adrian Hunter
2022-05-17 3:13 ` Namhyung Kim
2022-05-17 4:54 ` Adrian Hunter
2022-05-13 9:02 ` [PATCH 4/6] perf script: " Adrian Hunter
2022-05-13 9:02 ` [PATCH 5/6] perf kvm report: " Adrian Hunter
2022-05-13 9:02 ` [PATCH 6/6] perf intel-pt: " Adrian Hunter
2022-05-13 14:46 ` Andi Kleen
2022-05-13 15:14 ` Adrian Hunter
2022-05-13 18:13 ` Andi Kleen [this message]
2022-05-15 7:27 ` Adrian Hunter
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=871qwxgv1e.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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 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.