linux-um archives
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
Cc: Glenn Washburn <development@efficientek.com>,
	 linux-um <linux-um@lists.infradead.org>,
	 Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Using ftrace
Date: Tue, 31 Jan 2023 08:22:45 +0100 (CET)	[thread overview]
Message-ID: <1215849138.84344.1675149765214.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <aa957c80-1aeb-8fde-440e-6e4408c59559@kot-begemot.co.uk>

----- Ursprüngliche Mail -----
> Von: "Anton Ivanov" <anton.ivanov@kot-begemot.co.uk>
> On 31/01/2023 04:17, Glenn Washburn wrote:
>> I'm trying to use the ftrace facility within UML. It appears as though
>> it exists in the menuconfig, but I can't seem to get the kernel to
>> recognize the tracefs filesystem. I'm wondering if someone can confirm
>> that either ftrace does or does not work in UML.
> 
> I have not used it. We have not had any requests related to it either
> 
> I will look into it.

Tracing itself should work. But function tracing is not supported.
You'll get tracefs as soon you select one tracer (such as CONFIG_IRQSOFF_TRACER).

Adding function (and function graph) tracing to UML is possible but a bit of work.
You need to find a way to implement all of ftraces mcount hooks for UML.

Thanks,
//richard

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

  reply	other threads:[~2023-01-31  7:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  4:17 Using ftrace Glenn Washburn
2023-01-31  6:47 ` Anton Ivanov
2023-01-31  7:22   ` Richard Weinberger [this message]
2023-01-31  9:10     ` Johannes Berg
2023-01-31  9:52       ` Anton Ivanov
2023-01-31 22:05       ` YiFei Zhu
2023-01-31 18:44     ` Glenn Washburn

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=1215849138.84344.1675149765214.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --cc=development@efficientek.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-um@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox