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: <86802c440612192250l50805d40h71baa7ce6f99a3e5@mail.gmail.com>
Date:	Tue, 19 Dec 2006 22:50:33 -0800
From:	"Yinghai Lu" <yinghai.lu@....com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Tobias Diedrich" <ranma+kernel@...edrich.de>,
	"Linus Torvalds" <torvalds@...l.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andi Kleen" <ak@...e.de>, "Andrew Morton" <akpm@...l.org>
Subject: Re: IO-APIC + timer doesn't work

On 12/19/06, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> So the pin2 case should be tested right after the pin1 case as we do
> currently.  On most new boards that will be a complete noop.
>
> But it is better than our current blind guess at using ExtINT mode.
>
> I figure after we try what the BIOS has told us about and that
> has failed we should first try the common irq 0 apic mappings,
> and then try the common ExtINT mappings.

Please check if this one is ok.

View attachment "timers_12192006.patch" of type "text/x-patch" (6199 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ