[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150901153518.6de77eb0@gandalf.local.home>
Date: Tue, 1 Sep 2015 15:35:18 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shaohua Li <shli@...com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
John Stultz <john.stultz@...aro.org>,
lkml <linux-kernel@...r.kernel.org>,
Prarit Bhargava <prarit@...hat.com>,
Richard Cochran <richardcochran@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
"Ingo Molnar" <mingo@...nel.org>,
Clark Williams <williams@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 8/9] clocksource: Improve unstable clocksource detection
On Tue, 1 Sep 2015 11:14:17 -0700
Shaohua Li <shli@...com> wrote:
> > You think that blocking softirq execution for 42.9 seconds is normal?
> > Seems we are living in a different universe.
>
> I don't say it's normal. I say it's not hard to trigger.
>
> > > it's just VM off. A softirq can hog the cpu.
> >
Please provide a test case that shows the softirq hogging the cpu for
over 40 seconds.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists