linux-kernel - Re: [PATCH 8/8] irq: make ht irq

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: <1239924898.27006.8466.camel@localhost.localdomain>
Date:	Thu, 16 Apr 2009 16:34:58 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 8/8] irq: make ht irq_desc numa aware

On Thu, 2009-04-16 at 02:21 -0700, Ingo Molnar wrote:
> The whole series has become very reasonable (modulo the minor 
> structure and Cc: related comments i made).
> 
> It's obviously too late in .30 to push it upstream, so the best 
> action is to mark it broken upstream, then remove + rewrite it in 
> the IRQ tree and we'll have all this done properly in v2.6.31.
> 
> Thomas, Eric, Suresh, what do you think?

Instead of marking the NUMA_MIGRATE_IRQ_DESC config option broken, I
would like to see it removed in 2.6.30 (i.e., apply the first patch in
this patchset for 2.6.30). As this simplifies quite a bit of code, this
will help anyone debugging a problem in this irq handling area, during
the life span of any distro carrying this kernel version.

thanks,
suresh

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