public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/7] perf/trace: Add notification for perf trace events
Date: Wed, 31 Aug 2016 12:01:58 +0100	[thread overview]
Message-ID: <87bn09mcbd.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <1471344312-26685-2-git-send-email-punit.agrawal@arm.com> (Punit Agrawal's message of "Tue, 16 Aug 2016 11:45:06 +0100")

Punit Agrawal <punit.agrawal@arm.com> writes:

> Add a mechanism to notify listeners about perf trace event state
> changes. This enables listeners to take actions requiring the event
> context (e.g., attached process).
>
> The notification mechanism can be used to reduce trace point based
> profiling overhead by enabling/disabling hardware traps for specific
> contexts (e.g., virtual machines).
>
> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Ingo Molnar <mingo@redhat.com>

While I respin the series addressing comments on the arm64 architectural
bits, I'd appreciate any feedback on this patch as it forms the basis of
the rest of the series.

Thanks,
Punit

> ---
>  include/linux/trace_events.h    |  3 +++
>  kernel/trace/trace_event_perf.c | 24 ++++++++++++++++++++++++
>  2 files changed, 27 insertions(+)
>
> diff --git a/include/linux/trace_events.h b/include/linux/trace_events.h
> index be00761..5924032 100644
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -505,6 +505,9 @@ perf_trace_buf_submit(void *raw_data, int size, int rctx, u16 type,
>  {
>  	perf_tp_event(type, count, raw_data, size, regs, head, rctx, task);
>  }
> +
> +extern int perf_trace_notifier_register(struct notifier_block *nb);
> +extern int perf_trace_notifier_unregister(struct notifier_block *nb);
>  #endif
>  
>  #endif /* _LINUX_TRACE_EVENT_H */
> diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> index 562fa69..9aaaacf 100644
> --- a/kernel/trace/trace_event_perf.c
> +++ b/kernel/trace/trace_event_perf.c
> @@ -6,10 +6,12 @@
>   */
>  
>  #include <linux/module.h>
> +#include <linux/notifier.h>
>  #include <linux/kprobes.h>
>  #include "trace.h"
>  
>  static char __percpu *perf_trace_buf[PERF_NR_CONTEXTS];
> +static RAW_NOTIFIER_HEAD(perf_trace_notifier_list);
>  
>  /*
>   * Force it to be aligned to unsigned long to avoid misaligned accesses
> @@ -86,6 +88,26 @@ static int perf_trace_event_perm(struct trace_event_call *tp_event,
>  	return 0;
>  }
>  
> +int perf_trace_notifier_register(struct notifier_block *nb)
> +{
> +	return raw_notifier_chain_register(&perf_trace_notifier_list, nb);
> +}
> +
> +int perf_trace_notifier_unregister(struct notifier_block *nb)
> +{
> +	return raw_notifier_chain_unregister(&perf_trace_notifier_list, nb);
> +}
> +
> +static void perf_trace_notify(enum trace_reg event, struct perf_event *p_event)
> +{
> +	/*
> +	 * We use raw notifiers here as we are called with the
> +	 * event_mutex held.
> +	 */
> +	raw_notifier_call_chain(&perf_trace_notifier_list,
> +				     event, p_event);
> +}
> +
>  static int perf_trace_event_reg(struct trace_event_call *tp_event,
>  				struct perf_event *p_event)
>  {
> @@ -176,6 +198,7 @@ out:
>  static int perf_trace_event_open(struct perf_event *p_event)
>  {
>  	struct trace_event_call *tp_event = p_event->tp_event;
> +	perf_trace_notify(TRACE_REG_PERF_OPEN, p_event);
>  	return tp_event->class->reg(tp_event, TRACE_REG_PERF_OPEN, p_event);
>  }
>  
> @@ -183,6 +206,7 @@ static void perf_trace_event_close(struct perf_event *p_event)
>  {
>  	struct trace_event_call *tp_event = p_event->tp_event;
>  	tp_event->class->reg(tp_event, TRACE_REG_PERF_CLOSE, p_event);
> +	perf_trace_notify(TRACE_REG_PERF_CLOSE, p_event);
>  }
>  
>  static int perf_trace_event_init(struct trace_event_call *tp_event,

  reply	other threads:[~2016-08-31 11:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 10:45 [RFC PATCH 0/7] Add support for monitoring guest TLB operations Punit Agrawal
2016-08-16 10:45 ` [RFC PATCH 1/7] perf/trace: Add notification for perf trace events Punit Agrawal
2016-08-31 11:01   ` Punit Agrawal [this message]
2016-08-16 10:45 ` [RFC PATCH 2/7] KVM: Track the pid of the VM process Punit Agrawal
2016-08-16 10:45 ` [RFC PATCH 3/7] KVM: arm/arm64: Register perf trace event notifier Punit Agrawal
2016-08-16 10:45 ` [RFC PATCH 4/7] arm64: tlbflush.h: add __tlbi() macro Punit Agrawal
2016-08-19 13:24   ` Will Deacon
2016-08-19 13:34     ` Punit Agrawal
2016-08-16 10:45 ` [RFC PATCH 5/7] arm64/kvm: hyp: tlb: use __tlbi() helper Punit Agrawal
2016-08-16 10:45 ` [RFC PATCH 6/7] arm64: KVM: Handle trappable TLB instructions Punit Agrawal
2016-08-19 15:18   ` Will Deacon
2016-08-24 10:40     ` Punit Agrawal
2016-08-26  9:37       ` Punit Agrawal
2016-08-26 12:21         ` Marc Zyngier
2016-09-01 14:55         ` Will Deacon
2016-09-01 18:29           ` Punit Agrawal
2016-08-16 10:45 ` [RFC PATCH 7/7] arm64: KVM: Enable selective trapping of " Punit Agrawal
2016-08-17 15:58 ` [RFC PATCH 0/7] Add support for monitoring guest TLB operations Paolo Bonzini
2016-08-17 17:01   ` Punit Agrawal
2016-08-17 17:02     ` Paolo Bonzini
2016-08-17 17:20       ` Punit Agrawal
2016-08-18  7:04         ` Paolo Bonzini

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=87bn09mcbd.fsf@e105922-lin.cambridge.arm.com \
    --to=punit.agrawal@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=will.deacon@arm.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