linux-kernel - RE: [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when check

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]

Date:	Mon, 8 Jan 2007 09:16:32 -0800
From:	"Lu, Yinghai" <yinghai.lu@....com>
To:	ebiederm@...ssion.com, "Linus Torvalds" <torvalds@...l.org>
cc:	"Tobias Diedrich" <ranma+kernel@...edrich.de>,
	"Andrew Morton" <akpm@...l.org>, "Adrian Bunk" <bunk@...sta.de>,
	"Andi Kleen" <ak@...e.de>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when
 check_timer fails.

-----Original Message-----
From: ebiederm@...ssion.com [mailto:ebiederm@...ssion.com] 
Sent: Monday, January 08, 2007 8:11 AM
To: Linus Torvalds
Cc: Tobias Diedrich; Lu, Yinghai; Andrew Morton; Adrian Bunk; Andi
Kleen; Linux Kernel Mailing List
Subject: [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when
check_timer fails.

>I have tested this on an Nvidia board that reports that apic 0 pin 2
>works when it does not and this code successfully programs apic 0 pin 0
>into ExtINT mode.

For some CK804 boards, BIOS forget set to 8254 timer to apic0/pin2, and
still leave it at apic0/pin0. but mptable and acpi said 8254 timer is to
apic0/pin2. At such case we should try apic0/pin0 with INT mode instead
of ExtINT mode.

YH




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