linux-kernel - Re: fused X86_UP_APIC and X86_UP

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: <4D564D6F.3090900@nachtwindheim.de>
Date:	Sat, 12 Feb 2011 10:05:51 +0100
From:	Henrik Kretzschmar <henrik@...htwindheim.de>
To:	Henrik Kretzschmar <henne@...htwindheim.de>
CC:	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	x86@...nel.org
Subject: Re: fused  X86_UP_APIC and  X86_UP_IOAPIC ?

Am 10.02.2011 11:35, schrieb Henrik Kretzschmar:
>> In commit 7cd92366a593246650cc7d6198e2c7d3af8c1d8a (x86/Voyager: remove APIC/IO-APIC Kbuild quirk / just before 2.6.29-rc4)
>> Ingo replaced the X86_UP_IOAPIC with X86_UP_APIC.
>> 
>> Was this intended ord by accident?

* Ingo Molnar <mingo@...hat.com> wrote:
> Mind sending a patch against the latest x86 tree.

Yes, I do, but just changing the config makes the compilation break,
so some prior steps are needed, since X86_APIC and X86_IO_APIC 
have fused a bit too much.

But I'm confident.

Greets,
Henrik 
--
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/