linux-kernel - Re: [PATCH 4/6] watchdog: Boot-disable by default on full dynticks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130613152059.GA133453@redhat.com>
Date:	Thu, 13 Jun 2013 11:20:59 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Li Zhong <zhong@...ux.vnet.ibm.com>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Anish Singh <anish198519851985@...il.com>
Subject: Re: [PATCH 4/6] watchdog: Boot-disable by default on full dynticks

On Thu, Jun 13, 2013 at 04:56:03PM +0200, Frederic Weisbecker wrote:
> > > > Peter,
> > > > 
> > > > Where is this patch?
> > > 
> > > Which patch? The old version of the current one? It was part of a previous series
> > > that needed improvements so it hasn't been applied yet.
> > 
> > I guess I am confused.  I thought Peter said in an email awhile ago, that
> > he found Stephan's patch (that converted perf to use hrtimers) and applied
> > it to his tree.  Are you saying it was unapplied because it needed
> > improvements?
> 
> I think it doesn't completely remove the perf tick. Besides it doesn't really
> solve the problem since perf events will require periodic hrtimers to work,
> which still defeats the purpose of full dynticks.

I don't know enough about how full dynticks work to even present a
solution.  But currently I was working with the Red Hat performance team
to enhance perf to help our customers diagnose performance problems
easier.

My fear is anyone who uses full dynticks and has issues, can't use perf to
help diagnose their problems because it will change the dynamics of the
problem.  And with the current huge drop in performance in cpu_idle (as
compared to RHEL-6's 2.6.32 kernel) due to what seems to be miscalculated
c-states, one might have a hard time evaluating if full dynticks is doing
the right thing or not.

Then again perhaps full dynticks isn't useful for distros like RHEL.

That's why I was hoping to solve the underlying problem as opposed to
accepting patches like this which work around the symptoms.

Again, my knowledge of full dynticks is poor, so I have almost no idea of
the complexities surrounding the problem and how hard it is to even solve
it.

Cheers,
Don

--
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/