linux-kernel - Re: [PATCH 2/8] [nmi watchdog] touch_softlockup cleanups and softlockup

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]

Date:	Thu, 13 May 2010 01:38:14 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Frederic Weisbecker <fweisbec@...il.com>, mingo@...e.hu
Cc:	Don Zickus <dzickus@...hat.com>, peterz@...radead.org,
	aris@...hat.com, linux-kernel@...r.kernel.org,
	randy.dunlap@...cle.com
Subject: Re: [PATCH 2/8] [nmi watchdog] touch_softlockup cleanups and
	softlockup_tick removal

On Wed, May 12, 2010 at 11:00:36PM +0200, Frederic Weisbecker wrote:
...
> > > 
> > > Ah right.
> > > 
> > > BTW, if you address my reviews, please do it incrementally, I'm going
> > > to apply this set and push it to Ingo.
> > 
> > Ok, probably easier to review too. :-)
> 
> 
> Yeah, and it's time to flush this code as it's good globally.
> 
> Plus it would be nice to get this for .35
> 
> Ah and forget about the sysctl ABI breakages. Since this is only
> used for kernel development, this is not going to break much things.
> If somebody complains, we can still reintegrate what we had.
> 
> Thanks.
> 
...
Guys, could you please spend a few minutes and enlighten me a bit?
Does all this series mean that we eventually will drop nmi-watchdog
via io-apic (read via pic) as only the transition to perf complete?

I recall someone said about to stop using io-apic, but just to be sure.

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