From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Thomas <pthomas8589@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
dunc.mcphie@gmail.com, Anders Roxell <anders.roxell@linaro.org>
Subject: Re: poor cyclictest results with 5.0 series rt for arm64
Date: Wed, 17 Jul 2019 01:14:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1907170111160.1767@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAD56B7eF_KhWvg=m6iy5YSJF-81v-zcmX7+8Kd0wGMrALHwU1A@mail.gmail.com>
On Tue, 16 Jul 2019, Paul Thomas wrote:
> > > We do have trace data for a instance where cyclictest hit 5000 uS, but
> > > the file is large 11MB, and I wasn't sure if I should directly attach
> > > it to the email. What is the best way to post or send this?
> >
> > Can you upload the trace to some place? If you don't have storage, just use
> > bugzilla.kernel.org and open a bug, attach it and post a reference.
>
> Hi Thomas,
>
> I've put the last 60k line of the trace on the bug report here:
> https://bugzilla.kernel.org/show_bug.cgi?id=204189
>
> Just looking at the timestamp time of cyclicte-2778 I can see the last
> two finish_task_switch calls are seperated by 5801 uS. Is just before
> that the correct place to be looking?
Right. If I'm reading it correctly, I think I know what's wrong. Can you
please revert:
80e7f3b05365 ("arch/arm64: Add lazy preempt support")
Either that patch is broken or it got broken on forward porting it from
4.19. Need to look with brain awake tomorrow.
Thanks,
tglx
next prev parent reply other threads:[~2019-07-16 23:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 11:18 poor cyclictest results with 5.0 series rt for arm64 Paul Thomas
[not found] ` <CAD56B7c2=95r7r-6tr0Mby8jSeuQPDNSd4LELnUw1LVRn9Rqew@mail.gmail.com>
2019-07-12 11:32 ` Paul Thomas
2019-07-16 20:24 ` Thomas Gleixner
2019-07-16 21:50 ` Paul Thomas
2019-07-16 23:14 ` Thomas Gleixner [this message]
2019-07-17 0:44 ` Paul Thomas
2019-07-17 8:03 ` Thomas Gleixner
2019-07-17 8:10 ` Thomas Gleixner
2019-07-17 9:02 ` Thomas Gleixner
2019-07-17 10:21 ` Thomas Gleixner
2019-07-17 22:28 ` Paul Thomas
2019-08-13 9:53 ` Sebastian Andrzej Siewior
2019-08-13 18:02 ` Paul Thomas
2019-08-14 11:26 ` Sebastian Andrzej Siewior
2019-08-14 16:17 ` [PATCH RT] arm64: preempt: Check preemption level before looking at lazy-preempt Sebastian Andrzej Siewior
2019-08-14 16:17 ` [PATCH RT] x86: " Sebastian Andrzej Siewior
2019-08-14 17:04 ` poor cyclictest results with 5.0 series rt for arm64 Paul Thomas
2019-08-15 8:29 ` Sebastian Andrzej Siewior
2019-08-15 12:33 ` John Ogness
2019-08-15 13:30 ` Paul Thomas
2019-08-15 13:42 ` Sebastian Andrzej Siewior
2019-08-15 13:52 ` Paul Thomas
2019-08-15 14:19 ` Sebastian Andrzej Siewior
2019-08-15 15:12 ` Paul Thomas
2019-08-15 15:15 ` Sebastian Andrzej Siewior
2019-08-15 15:31 ` Paul Thomas
2019-08-15 18:00 ` Paul Thomas
2019-08-15 18:57 ` Sebastian Andrzej Siewior
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=alpine.DEB.2.21.1907170111160.1767@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=anders.roxell@linaro.org \
--cc=dunc.mcphie@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=pthomas8589@gmail.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).