public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Michael Opdenacker <michael-lists@free-electrons.com>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Linux-tiny@selenic.com
Subject: Re: [PATCH] x86 (Linux Tiny): configure out support for	some	processors
Date: Mon, 11 Feb 2008 16:54:30 -0800	[thread overview]
Message-ID: <47B0EE46.6050208@zytor.com> (raw)
In-Reply-To: <1202772532.12383.67.camel@cinder.waste.org>

Matt Mackall wrote:
> On Mon, 2008-02-11 at 15:01 -0800, H. Peter Anvin wrote:
>> Matt Mackall wrote:
>>> Best would be to have no ifdefs and do it all with linker magic, of
>>> course. But that's trickier.
>>>
>> I concur with this, definitely.
> 
> Ok, so let's come up with a plan. We can:
> 
> a) use weak symbols, ala cond_syscall
> b) use a special section
> c) use early_init code (is it early enough?)
> c) have some sort of registration list
> 
> Having a generic cond_call of some sort might be nice for this sort of
> thing.
> 

c) is out, because this has to be executed after the early generic code 
and before the late generic code.

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.

	-hpa


  reply	other threads:[~2008-02-12  1:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 22:47 [PATCH] x86 (Linux Tiny): configure out support for some processors Michael Opdenacker
2008-02-08 23:04 ` H. Peter Anvin
2008-02-08 23:11 ` Ingo Molnar
2008-02-09  9:31   ` Michael Opdenacker
2008-02-11 22:42   ` Michael Opdenacker
2008-02-11 22:56     ` Matt Mackall
2008-02-11 23:01       ` H. Peter Anvin
2008-02-11 23:28         ` Matt Mackall
2008-02-12  0:54           ` H. Peter Anvin [this message]
2008-02-12  1:15             ` Matt Mackall
2008-02-15 11:00             ` [RFC] [PATCH] x86: Use ELF section to list CPU vendor specific code (Linux Tiny) Thomas Petazzoni
2008-02-17 18:14               ` Ingo Molnar
2008-02-17 19:46                 ` H. Peter Anvin
2008-02-23  2:43               ` Matt Mackall
2008-02-23  3:19                 ` H. Peter Anvin
2008-02-25  8:29                 ` Thomas Petazzoni
2008-02-25 17:03                   ` Matt Mackall
2008-02-25 17:53                     ` Thomas Petazzoni
2008-02-25 17:58                       ` Matt Mackall
2008-02-11 22:59     ` [PATCH] x86 (Linux Tiny): configure out support for some processors H. Peter Anvin
2008-02-08 23:20 ` Matt Mackall
2008-02-09  8:30   ` Simon Holm Thøgersen
2008-02-09  9:29     ` Michael Opdenacker
2008-02-09 10:05       ` Simon Holm Thøgersen
2008-02-09 21:35       ` H. Peter Anvin
2008-02-09  9:26   ` Michael Opdenacker
2008-02-09  3:48 ` Taral

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47B0EE46.6050208@zytor.com \
    --to=hpa@zytor.com \
    --cc=Linux-tiny@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael-lists@free-electrons.com \
    --cc=mingo@elte.hu \
    --cc=mpm@selenic.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox