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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20130613140207.GW133453@redhat.com>
Date:	Thu, 13 Jun 2013 10:02:07 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <peterz@...radead.org>
Cc:	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 03:10:59PM +0200, Frederic Weisbecker wrote:
> On Wed, Jun 12, 2013 at 01:03:16PM -0400, Don Zickus wrote:
> > On Wed, Jun 12, 2013 at 04:02:36PM +0200, Frederic Weisbecker wrote:
> > > When the watchdog runs, it prevents the full dynticks
> > > CPUs from stopping their tick because the hard lockup
> > > detector uses perf events internally, which in turn
> > > rely on the periodic tick.
> > > 
> > > Since this is a rather confusing behaviour that is not
> > > easy to track down and identify for those who want to
> > > test CONFIG_NO_HZ_FULL, let's default disable the
> > > watchdog on boot time when full dynticks is enabled.
> > > 
> > > The user can still enable it later on runtime using
> > > proc or sysctl.
> > 
> > I thought we had a conversation awhile ago, where we agreed this was going
> > to be fixed for 3.11?  Didn't Peter find the patch and apply it to his
> > tree?  I am confused why this is still needed?
> 
> We agreed on the patch but it hasn't been applied yet. I'm trying to get
> a sane series of nohz patches before sending to Ingo.

Peter,

Where is this patch?

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/