From: Lei YU <mine260309@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: taoren@fb.com, cov@fb.com, Andrew Jeffery <andrew@aj.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
daniel.lezcano@linaro.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linus.walleij@linaro.org
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix set_next_event handler
Date: Fri, 21 Sep 2018 14:22:01 +0800 [thread overview]
Message-ID: <CAARXrtmpUn3DKguiQSubZvCM3sJ--QxtzoYVoEvC-81udH7BLA@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XeEZeMskkxNChhNSO+brpoPJ5FqweWNXe22BpyytwCwFw@mail.gmail.com>
> >
> > Make sense. I actually booted up kernel on qemu-palmetto (ast2400) but I'm doubting if test is valid because it depends on how qemu emulates the hardware. It would be great if someone can help to verify the patch on physical ast2400.
>
> I gave this a spin on the ast2400. It looked okay, but I was wondering
> if you could share you test case so I can run the same test?
Tested on Palmetto (OpenPOWER P8 with AST2400), and it does show the fix is
working on AST2400 as well.
Without the patch, usleep(100) takes tens of milliseconds randomly;
With the patch, usleep(100) takes about 600~700 microseconds stably.
Tested-by: Lei YU <mine260309@gmail.com>
next prev parent reply other threads:[~2018-09-21 6:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 22:13 Tao Ren
2018-09-19 23:16 ` Daniel Lezcano
2018-09-20 15:45 ` Linus Walleij
2018-09-20 21:09 ` Tao Ren
2018-09-21 3:32 ` Joel Stanley
2018-09-21 6:22 ` Lei YU [this message]
2018-09-21 18:11 ` Tao Ren
2018-09-21 18:11 ` Tao Ren
2018-09-24 23:20 ` Joel Stanley
2018-09-25 0:40 ` Tao Ren
2018-09-25 17:13 ` Sai Dasari
2018-09-25 19:16 ` Linus Walleij
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=CAARXrtmpUn3DKguiQSubZvCM3sJ--QxtzoYVoEvC-81udH7BLA@mail.gmail.com \
--to=mine260309@gmail.com \
--cc=andrew@aj.id.au \
--cc=cov@fb.com \
--cc=daniel.lezcano@linaro.org \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®