From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] m68k: Add tracirqs
Date: Wed, 23 Oct 2024 11:13:19 +0200 [thread overview]
Message-ID: <CAMuHMdXKCWnFuyOzQyAWdEV4EhqXYXJFn4vCw5ptZ5=sbOCbxg@mail.gmail.com> (raw)
In-Reply-To: <262d7758-c752-49f6-87ef-4f75d681a919@yoseli.org>
Hi Jean-Michel,
On Wed, Oct 23, 2024 at 11:07 AM Jean-Michel Hautbois
<jeanmichel.hautbois@yoseli.org> wrote:
> On 23/10/2024 10:47, Steven Rostedt wrote:
> > On Tue, 22 Oct 2024 11:21:34 +0200
> > Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org> wrote:
> >> I was not really expecting you to review the m68k one no :-).
> >> I think I have other issues which might have impact on ftrace too.
> >> For instance, when I launch cyclictest I have a warning about HRTIMERS:
> >> # cyclictest -p 99
> >> WARN: stat /dev/cpu_dma_latency failed: No such file or directory
> >> WARN: High resolution timers not available
> >> policy: fifo: loadavg: 1.21 0.40 0.14 1/122 245
> >>
> >> T: 0 ( 245) P:99 I:1000 C: 11203 Min: 92 Act: 623 Avg: 775 Max:
> >> 3516
> >>
> >> The latencies are quite high...
> >
> > Yes, if you don't have high resolution timers, the latency will be high.
>
> According to my config, I should have those:
> CONFIG_HIGH_RES_TIMERS=y
Does your hardware have a high resolution timer, and do you have
a driver for it?
$ git grep hrtimer -- arch/m68k/
$
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-10-23 9:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 9:44 [PATCH RFC 0/2] Add basic tracing support for m68k Jean-Michel Hautbois
2024-10-21 9:44 ` [PATCH RFC 1/2] m68k: Add tracirqs Jean-Michel Hautbois
2024-10-22 5:28 ` Steven Rostedt
2024-10-22 5:42 ` Jean-Michel Hautbois
2024-10-22 8:30 ` Steven Rostedt
2024-10-22 9:21 ` Jean-Michel Hautbois
2024-10-23 8:47 ` Steven Rostedt
2024-10-23 9:07 ` Jean-Michel Hautbois
2024-10-23 9:13 ` Geert Uytterhoeven [this message]
2024-10-23 9:31 ` Jean-Michel Hautbois
2024-10-23 10:30 ` Jean-Michel Hautbois
2024-10-23 3:53 ` Michael Schmitz
2024-10-23 5:53 ` Jean-Michel Hautbois
2024-10-23 7:30 ` Michael Schmitz
2024-10-23 8:59 ` Jean-Michel Hautbois
2024-10-23 9:27 ` Steven Rostedt
2024-10-23 8:51 ` Eero Tamminen
2024-10-21 9:44 ` [PATCH RFC 2/2] arch: m68k: Add STACKTRACE support Jean-Michel Hautbois
2024-11-27 11:26 ` Jean-Michel Hautbois
2024-12-02 14:41 ` Greg Ungerer
2024-12-02 14:51 ` Jean-Michel Hautbois
2024-12-02 14:52 ` Jean-Michel Hautbois
2024-12-02 23:01 ` Greg Ungerer
2024-12-03 6:25 ` Jean-Michel Hautbois
2024-12-02 17:53 ` Jean-Michel Hautbois
2024-11-15 8:26 ` [PATCH RFC 0/2] Add basic tracing support for m68k Jean-Michel Hautbois
2024-11-15 15:25 ` Steven Rostedt
2024-11-15 15:33 ` Jean-Michel Hautbois
2024-11-15 19:55 ` Steven Rostedt
2024-11-18 10:11 ` Jean-Michel Hautbois
2024-11-18 20:20 ` Steven Rostedt
2024-11-19 14:24 ` Jean-Michel Hautbois
2024-11-19 15:26 ` Steven Rostedt
2024-11-19 16:28 ` Steven Rostedt
2024-11-19 16:44 ` Steven Rostedt
2024-11-19 18:06 ` Jean-Michel Hautbois
2024-11-19 18:10 ` Steven Rostedt
2024-11-20 11:47 ` Jean-Michel Hautbois
2024-11-20 15:31 ` Steven Rostedt
2024-11-20 15:59 ` Jean-Michel Hautbois
2024-11-20 16:43 ` Steven Rostedt
2024-11-20 16:51 ` Jean-Michel Hautbois
2024-11-19 18:25 ` Michael Schmitz
2024-11-28 15:25 ` Tomas Glozar
2024-12-02 12:53 ` Jean-Michel Hautbois
2024-12-02 14:45 ` Tomas Glozar
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='CAMuHMdXKCWnFuyOzQyAWdEV4EhqXYXJFn4vCw5ptZ5=sbOCbxg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-trace-kernel@vger.kernel.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 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).