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

Message-ID: <m1wt3xgsax.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 08 Jan 2007 13:46:46 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Lu, Yinghai" <yinghai.lu@....com>
Cc:	"Linus Torvalds" <torvalds@...l.org>,
	"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.

"Lu, Yinghai" <yinghai.lu@....com> writes:

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

Duh.  I forgot Nvidia provided a register like that, now I am
beginning to understand what is wrong.  Anyway we do try apic0 pin0 by
default on the Nvidia's because of a Nvidia specific work around.

So that doesn't invalidate the generic test.  I'm going to go dig
out what little information I have and see if I can stair at the
register definition.

Anyway that doesn't invalidate anything in this patch. 

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