From: Quan Zhou <zhouquan@iscas.ac.cn>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-perf-users@vger.kernel.org, anup@brainfault.org,
atishp@atishpatra.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org
Subject: Re: [PATCH 1/2] riscv: perf: add guest vs host distinction
Date: Fri, 19 Jul 2024 17:50:18 +0800 [thread overview]
Message-ID: <a78bb55e-ae7d-47ad-a3fc-f4662f42625f@iscas.ac.cn> (raw)
In-Reply-To: <20240718-e689be134be5b958b1eec65a@orel>
On 2024/7/19 00:53, Andrew Jones wrote:
> On Thu, Jul 18, 2024 at 07:23:41PM GMT, zhouquan@iscas.ac.cn wrote:
>> From: Quan Zhou <zhouquan@iscas.ac.cn>
>>
>> Introduce basic guest support in perf, enabling it to distinguish
>> between PMU interrupts in the host or guest, and collect
>> fundamental information.
>>
>> Signed-off-by: Quan Zhou <zhouquan@iscas.ac.cn>
>> ---
>> arch/riscv/include/asm/perf_event.h | 7 ++++++
>> arch/riscv/kernel/perf_callchain.c | 38 +++++++++++++++++++++++++++++
>> 2 files changed, 45 insertions(+)
>>
>> diff --git a/arch/riscv/include/asm/perf_event.h b/arch/riscv/include/asm/perf_event.h
>> index 665bbc9b2f84..5866d028aee5 100644
>> --- a/arch/riscv/include/asm/perf_event.h
>> +++ b/arch/riscv/include/asm/perf_event.h
>> @@ -8,13 +8,20 @@
>> #ifndef _ASM_RISCV_PERF_EVENT_H
>> #define _ASM_RISCV_PERF_EVENT_H
>>
>> +#ifdef CONFIG_PERF_EVENTS
>> #include <linux/perf_event.h>
>> #define perf_arch_bpf_user_pt_regs(regs) (struct user_regs_struct *)regs
>>
>> +extern unsigned long perf_instruction_pointer(struct pt_regs *regs);
>> +extern unsigned long perf_misc_flags(struct pt_regs *regs);
>> +#define perf_misc_flags(regs) perf_misc_flags(regs)
>> +
>> #define perf_arch_fetch_caller_regs(regs, __ip) { \
>
> Arm has this outside the #ifdef CONFIG_PERF_EVENTS, but it doesn't
> look like it should be.
>
Yes, Arm makes perf_arch_fetch_caller_regs independent of
CONFIG_PERF_EVENTS. What is the rationale behind this? I'm
not clear on this point. It's reasonable to have them inside
for riscv, right?
>> (regs)->epc = (__ip); \
>> (regs)->s0 = (unsigned long) __builtin_frame_address(0); \
>> (regs)->sp = current_stack_pointer; \
>> (regs)->status = SR_PP; \
>> }
>> +#endif
>> +
>> #endif /* _ASM_RISCV_PERF_EVENT_H */
>> diff --git a/arch/riscv/kernel/perf_callchain.c b/arch/riscv/kernel/perf_callchain.c
>> index 3348a61de7d9..c673dc6d9bd2 100644
>> --- a/arch/riscv/kernel/perf_callchain.c
>> +++ b/arch/riscv/kernel/perf_callchain.c
>> @@ -58,6 +58,11 @@ void perf_callchain_user(struct perf_callchain_entry_ctx *entry,
>> {
>> unsigned long fp = 0;
>>
>> + if (perf_guest_state()) {
>> + /* TODO: We don't support guest os callchain now */
>> + return;
>> + }
>> +
>> fp = regs->s0;
>> perf_callchain_store(entry, regs->epc);
>>
>> @@ -74,5 +79,38 @@ static bool fill_callchain(void *entry, unsigned long pc)
>> void perf_callchain_kernel(struct perf_callchain_entry_ctx *entry,
>> struct pt_regs *regs)
>> {
>> + if (perf_guest_state()) {
>> + /* TODO: We don't support guest os callchain now */
>> + return;
>> + }
>> +
>> walk_stackframe(NULL, regs, fill_callchain, entry);
>> }
>> +
>> +unsigned long perf_instruction_pointer(struct pt_regs *regs)
>> +{
>> + if (perf_guest_state())
>> + return perf_guest_get_ip();
>> +
>> + return instruction_pointer(regs);
>> +}
>> +
>> +unsigned long perf_misc_flags(struct pt_regs *regs)
>> +{
>> + unsigned int guest_state = perf_guest_state();
>> + int misc = 0;
>
> Should use unsigned long for misc.
>
Okay, I'll fix it.
Thanks,
Quan
>> +
>> + if (guest_state) {
>> + if (guest_state & PERF_GUEST_USER)
>> + misc |= PERF_RECORD_MISC_GUEST_USER;
>> + else
>> + misc |= PERF_RECORD_MISC_GUEST_KERNEL;
>> + } else {
>> + if (user_mode(regs))
>> + misc |= PERF_RECORD_MISC_USER;
>> + else
>> + misc |= PERF_RECORD_MISC_KERNEL;
>> + }
>> +
>> + return misc;
>> +}
>> --
>> 2.34.1
>>
>
> Thanks,
> drew
next prev parent reply other threads:[~2024-07-19 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 11:23 [PATCH 0/2] Add perf support to collect KVM guest statistics from host side zhouquan
2024-07-18 11:23 ` [PATCH 1/2] riscv: perf: add guest vs host distinction zhouquan
2024-07-18 16:53 ` Andrew Jones
2024-07-19 9:50 ` Quan Zhou [this message]
2024-07-18 11:23 ` [PATCH 2/2] riscv: KVM: add basic support for host vs guest profiling zhouquan
2024-07-18 17:09 ` Andrew Jones
2024-07-19 9:55 ` Quan Zhou
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=a78bb55e-ae7d-47ad-a3fc-f4662f42625f@iscas.ac.cn \
--to=zhouquan@iscas.ac.cn \
--cc=ajones@ventanamicro.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=jolsa@kernel.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.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=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).