linux-kernel - Re: x86: unifying the 32 and 64 bit machine check handlers

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: <86802c440807011334u735ab53ep14c1039795eba5ec@mail.gmail.com>
Date:	Tue, 1 Jul 2008 13:34:41 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Max Asbock" <masbock@...ux.vnet.ibm.com>,
	"Andi Kleen" <andi@...stfloor.org>, mingo <mingo@...hat.com>,
	hpa <hpa@...or.com>, tglx <tglx@...utronix.de>,
	"Venki Pallipadi" <venkatesh.pallipadi@...el.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: x86: unifying the 32 and 64 bit machine check handlers

On Tue, Jul 1, 2008 at 1:09 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Max Asbock <masbock@...ux.vnet.ibm.com> wrote:
>
>> Is anybody currently working on combining the machine check handlers
>> for 32-bit and 64-bit x86? If there is interest I could post some
>> rough patches to get this started.
>
> sure, please do! I'd suggest to work against tip/master:
>
>   http://people.redhat.com/mingo/tip.git/README
>
> as there's tons of x86 changes queued up already.
>
> (ideally we'd like to see mcelog to work on 32-bit as well.)

suggest for now on:
merge should be change xxx_32.c xxx_64.c step by step till them become
all the same. So we can track the change for every file for both arch

like io_apic_32.c/io_apic_64.c apic_32.c/apic_64.c, sort the functions
at first...

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/