linux-kernel - Re: [PATCH] x86 apic: Ack all pending irqs when crashed/on kexec

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-next>] [day] [month] [year] [list]

Message-ID: <4C196A2F.5010604@zytor.com>
Date:	Wed, 16 Jun 2010 17:19:59 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Pan, Jacob jun" <jacob.jun.pan@...el.com>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"kerstin.jonsson" <kerstin.jonsson@...csson.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"jbohac@...ell.com" <jbohac@...ell.com>,
	Yinghai Lu <yinghai@...nel.org>,
	"mingo@...e.hu" <mingo@...e.hu>, Avi Kivity <avi@...hat.com>,
	"trenn@...e.de" <trenn@...e.de>
Subject: Re: [PATCH] x86 apic: Ack all pending irqs when crashed/on kexec
 - V5

On 06/16/2010 02:11 PM, Pan, Jacob jun wrote:
> 
> W.R.T. the loop limits, is it possible to use a default max_loops value in
> case when cpu_khz is not set? The reason is that on Moorestown platform
> we need to do an early APIC setup before tsc_init(), so cpu_khz is 0 at the
> time we setup local APIC. The result is that we hit WARN_ON(max_loops<= 0)
> on Moorestown for early APIC setup.
> 
> The early APIC setup is needed because Moorestown does not have a PIT and the
> system timer interrupts are routed via IOAPIC.
> 

Can't MRST install a quick ballpark value into cpu_khz?

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