public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, hare@suse.de,
	akpm@linux-foundation.org, tglx@linutronix.de, mingo@elte.hu,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: Add back _end symbol that is missing	from Symbol.map
Date: Sun, 08 Nov 2009 08:36:35 -0800	[thread overview]
Message-ID: <4AF6F393.5050002@zytor.com> (raw)
In-Reply-To: <20091108113805.GA11847@merkur.ravnborg.org>

On 11/08/2009 03:38 AM, Sam Ravnborg wrote:
> 
> I'm afraid this will break a RELOCTABLE i386 kernel.
> 
> We fixed this up some time ago where we had to
> move the symbol definition inside a section
> to prevent the symbol being absolute.
> 

It's also possible to have a whitelist of "known relative" symbols in
reloc.c, just as we have a blacklist of "known absolute" symbols.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


      parent reply	other threads:[~2009-11-08 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200911041519.nA4FJWEW030164@imap1.linux-foundation.org>
2009-11-08 11:07 ` [tip:x86/urgent] x86: Add back _end symbol that is missing from Symbol.map tip-bot for Hannes Reinecke
2009-11-08 11:38   ` Sam Ravnborg
2009-11-08 11:48     ` Ingo Molnar
2009-11-08 12:38       ` Sam Ravnborg
2009-11-08 12:42         ` Ingo Molnar
2009-11-09 18:40         ` H. Peter Anvin
2009-12-14 22:27           ` [tip:x86/urgent] x86: Regex support and known-movable symbols for relocs, fix _end tip-bot for H. Peter Anvin
2009-11-08 16:36     ` H. Peter Anvin [this message]

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=4AF6F393.5050002@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=sam@ravnborg.org \
    --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