[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47B88F05.10409@zytor.com>
Date: Sun, 17 Feb 2008 11:46:13 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Matt Mackall <mpm@...enic.com>, Linux-tiny@...enic.com,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC] [PATCH] x86: Use ELF section to list CPU vendor specific
code (Linux Tiny)
Ingo Molnar wrote:
> * Thomas Petazzoni <thomas.petazzoni@...e-electrons.com> wrote:
>
>> Le Mon, 11 Feb 2008 16:54:30 -0800,
>> "H. Peter Anvin" <hpa@...or.com> a écrit :
>>
>>> b) would be my first choice, and yes, it would be a good thing to
>>> have a generalized mechanism for this. For the registrant, it's
>>> pretty easy: just add a macro that adds a pointer to a named
>>> section. We then need a way to get the base address and length of
>>> each such section in order to be able to execute each function in
>>> sequence.
>> You'll find below a tentative patch that implements this. Tuple
>> (vendor, pointer to cpu_dev structure) are stored in a
>> x86cpuvendor.init section of the kernel, which is then read by the
>> generic CPU code in arch/x86/kernel/cpu/common.c to fill the
>> cpu_devs[] function.
>
> thanks, i've picked this up into x86.git. It all looks much cleaner and
> much more maintainable now. Peter, any objections?
>
Looks great to me.
-hpa
--
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/
Powered by blists - more mailing lists