From: Jiafei Pan <jiafei.pan@nxp.com>
To: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>,
Vladimir Oltean <olteanv@gmail.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>,
Colin King <colin.king@canonical.com>,
Jiafei Pan <jiafei.pan@nxp.com>
Subject: RE: [EXT] Re: stress-ng --hrtimers hangs system
Date: Mon, 22 Jun 2020 02:30:53 +0000 [thread overview]
Message-ID: <AM0PR04MB4772E9C0733F81FACF24C58D8A970@AM0PR04MB4772.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <11546107.O9o76ZdvQC@kmk0>
Thanks Kurt for your confirmation.
Best Regards,
Jiafei.
-----Original Message-----
From: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>
Sent: Saturday, June 20, 2020 4:08 PM
To: Vladimir Oltean <olteanv@gmail.com>; Jiafei Pan <jiafei.pan@nxp.com>
Cc: linux-rt-users@vger.kernel.org; lkml <linux-kernel@vger.kernel.org>; rcu@vger.kernel.org; Colin King <colin.king@canonical.com>; Jiafei Pan <jiafei.pan@nxp.com>
Subject: Re: [EXT] Re: stress-ng --hrtimers hangs system
Caution: EXT Email
Hi Jiafei,
On Friday, June 12, 2020 2:49:17 AM CEST Jiafei Pan wrote:
> Hi, Kurt,
>
> May I know whether you used "root" user to run stress-ng? using "root"
> user will change the scheduler to be "SCHED_RR", so would you please
> share test result with root and non-root users? Thanks.
Performed the test now as root and non-root user. Same result: No problem.
Thanks,
Kurt
prev parent reply other threads:[~2020-06-22 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:47 stress-ng --hrtimers hangs system Vladimir Oltean
2020-06-05 3:20 ` Paul E. McKenney
2020-06-05 10:12 ` Vladimir Oltean
2020-06-05 12:57 ` Kurt Kanzenbach
2020-06-05 13:19 ` Vladimir Oltean
2020-06-09 16:37 ` Vladimir Oltean
2020-06-10 5:57 ` Kurt Kanzenbach
2020-06-10 14:37 ` Vladimir Oltean
2020-06-12 0:49 ` [EXT] " Jiafei Pan
2020-06-20 8:08 ` Kurt Kanzenbach
2020-06-22 2:30 ` Jiafei Pan [this message]
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=AM0PR04MB4772E9C0733F81FACF24C58D8A970@AM0PR04MB4772.eurprd04.prod.outlook.com \
--to=jiafei.pan@nxp.com \
--cc=colin.king@canonical.com \
--cc=kurt.kanzenbach@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rcu@vger.kernel.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).