linux-kernel - Re: [patch 2/4] x86: Do not use hpet MSI as clockevent broadcast device

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: <4B4FCC33.2010100@zytor.com>
Date:	Thu, 14 Jan 2010 18:00:19 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Len Brown <lenb@...nel.org>,
	Mark Hounschell <markh@...pro.net>,
	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
	Alain Knaff <alain@...ff.lu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Li, Shaohua" <shaohua.li@...el.com>
Subject: Re: [patch 2/4] x86: Do not use hpet MSI as clockevent broadcast
 device

On 01/14/2010 05:39 PM, Venkatesh Pallipadi wrote:
> Current kernel uses hpet MSI interrupts as both percpu clockevent device
> and also as clockevent broadcast device in place of IRQ0 timer.
> There seems to be issues with HPET MSI usage on some platforms. So,
> restrict it to be only used as a percpu clockevent device.

Any ideas of which platforms?  It would help avoiding "cargo cult
programming" in the future.

Other than that, I presume this is a .33 patch?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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