All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, mhiramat@kernel.org,
	revest@chromium.org, rostedt@goodmis.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ftrace: Add sample with custom ops
Date: Mon, 6 Feb 2023 14:25:16 -0800	[thread overview]
Message-ID: <20230206222516.GA873421@roeck-us.net> (raw)
In-Reply-To: <20230103124912.2948963-4-mark.rutland@arm.com>

On Tue, Jan 03, 2023 at 12:49:12PM +0000, Mark Rutland wrote:
> When reworking core ftrace code or architectural ftrace code, it's often
> necessary to test/analyse/benchmark a number of ftrace_ops
> configurations. This patch adds a module which can be used to explore
> some of those configurations.
> 
> I'm using this to benchmark various options for changing the way
> trampolines and handling of ftrace_ops work on arm64, and ensuring other
> architectures aren't adversely affected.
> 
> For example, in a QEMU+KVM VM running on a 2GHz Xeon E5-2660
> workstation, loading the module in various configurations produces:
> 
...

> +++ b/samples/ftrace/ftrace-ops.c

...

> +static int __init ftrace_ops_sample_init(void)
> +{
> +	unsigned long flags = 0;
> +	ktime_t start, end;
> +	u64 period;
> +
...
> +
> +	period = ktime_to_ns(ktime_sub(end, start));
> +
> +	pr_info("Attempted %u calls to %ps in %lluns (%lluns / call)\n",
> +		nr_function_calls, tracee_relevant,
> +		period, period / nr_function_calls);
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^

Building csky:allmodconfig ... failed
--------------
Error log:
ERROR: modpost: "__udivdi3" [samples/ftrace/ftrace-ops.ko] undefined!

Guenter

  parent reply	other threads:[~2023-02-06 22:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 12:49 [PATCH v2 0/3] ftrace: Add sample code with dynamic ftrace_ops Mark Rutland
2023-01-03 12:49 ` [PATCH v2 1/3] ftrace: Maintain samples/ftrace Mark Rutland
2023-01-04 14:31   ` Masami Hiramatsu
2023-01-03 12:49 ` [PATCH v2 2/3] ftrace: Export ftrace_free_filter() to modules Mark Rutland
2023-01-04 14:51   ` Masami Hiramatsu
2023-01-04 15:30     ` Mark Rutland
2023-01-04 16:03       ` Steven Rostedt
2023-01-03 12:49 ` [PATCH v2 3/3] ftrace: Add sample with custom ops Mark Rutland
2023-01-04 14:56   ` Masami Hiramatsu
2023-02-06 22:25   ` Guenter Roeck [this message]
2023-02-07  9:33     ` Mark Rutland

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=20230206222516.GA873421@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=revest@chromium.org \
    --cc=rostedt@goodmis.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.