linux-kernel - Re: [PATCH] x86: set percpu cpu0 lpj to default

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:	Fri, 14 Jan 2011 14:29:42 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Greg KH <greg@...ah.com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Christoph Lameter <cl@...ux.com>,
	Jason Wessel <jason.wessel@...driver.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH] x86: set percpu cpu0 lpj to default

On 01/14/2011 02:16 PM, Greg KH wrote:
> On Fri, Jan 14, 2011 at 01:22:32PM -0800, Yinghai Lu wrote:
>>
>> We need to use udelay() in early stage.
> 
> I still don't agree with this.
> 
> Again, _please_ post your real patches that require this, after
> explaining exactly _why_ this is needed at all, and what real problem it
> is solving.
> 
> You seem to be totally ignoring this request I've made numerous times,
> which isn't appreciated at all.  So I'm guessing that we should also
> ignore your patches as well?

Please forget about those patches about disabling USB legacy early now.

the one is because 

echi debug port early serial console in drivers/usb/early/ehci-dbgp.c

is using udelay() in early stage.

and now udelay is relying to use loops_per_jiffy in per cpu area that not set yet.

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