From: David Ahern <dsahern@gmail.com>
To: Hemant Kumar <hemant@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
acme@kernel.org, mingo@kernel.org, sukadev@linux.vnet.ibm.com,
maddy@linux.vnet.ibm.com, srikar@linux.vnet.ibm.com,
paulus@samba.org, namhyung@kernel.org, jolsa@kernel.org,
peterz@infradead.org
Subject: Re: [RFC PATCH] perf/kvm: Guest Symbol Resolution for powerpc
Date: Tue, 16 Jun 2015 20:27:07 -0600 [thread overview]
Message-ID: <5580DAFB.4080304@gmail.com> (raw)
In-Reply-To: <5580CC69.2090200@linux.vnet.ibm.com>
On 6/16/15 7:24 PM, Hemant Kumar wrote:
> Because, this depends on the kernel tracepoint "kvm_hv:kvm_guest_exit".
> perf_prepare_sample() in the kernel side sets the event->header.misc
> field to
> PERF_RECORD_MISC_KERNEL through perf_misc_flags(pt_regs). In case of
> tracepoints which always get hit in the host kernel context, the
> perf_misc_flags() will always return PERF_RECORD_MISC_KERNEL.
>
> IMHO we will rather have to set the cpumode in the user space for this
> tracepoint
> and we can't depend on the event->header.misc field for this case.
>
> What would you suggest?
>
oh, right you are using a tracepoint for this. It does not have the
hooks to specify cpumode. Never mind.
next prev parent reply other threads:[~2015-06-17 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 2:50 [RFC PATCH] perf/kvm: Guest Symbol Resolution for powerpc Hemant Kumar
2015-06-16 14:53 ` David Ahern
2015-06-17 1:24 ` Hemant Kumar
2015-06-17 2:27 ` David Ahern [this message]
2015-06-16 15:38 ` Arnaldo Carvalho de Melo
2015-06-18 0:03 ` Hemant Kumar
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=5580DAFB.4080304@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
/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).