linux-kernel - Re: [RFC] x86: Cleanup prose of Documentation/i386/IO-APIC.txt

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: <20080414102824.GB20649@elte.hu>
Date:	Mon, 14 Apr 2008 12:28:24 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Nick Andrew <nick@...k-andrew.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [RFC] x86: Cleanup prose of Documentation/i386/IO-APIC.txt


* Nick Andrew <nick@...k-andrew.net> wrote:

> On Mon, Apr 14, 2008 at 11:46:03AM +0200, Ingo Molnar wrote:
> > * Nick Andrew <nick@...k-andrew.net> wrote:
> > > I wouldn't know that, but I still have to use 'noapic' to get my AMD 
> > > box to boot :-(
> > 
> > oh. If "noapic" is still necessary with x86/latest:
> > 
> >   http://people.redhat.com/mingo/x86.git/README
> 
> Thanks; I'll retest on latest then. I didn't realise the problem was 
> fixed.

just to make sure: nothing _specific_ was done in this area, this is 
just to make sure we'll both deal with the same codebase. But in 
general, if a box needs "noapic", that signals a bug we should try to 
solve in the kernel automatically (even if it's BIOS inflicted damage).

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