public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Hugh Dickins <hugh@veritas.com>
Cc: Mike Travis <travis@sgi.com>,
	linux-kernel@vger.kernel.org,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH] x86: BUILD_IRQ say .text to avoid .data.percpu
Date: Thu, 24 Jul 2008 12:44:59 +0200	[thread overview]
Message-ID: <20080724104459.GI28817@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0807211828470.26173@blonde.site>


* Hugh Dickins <hugh@veritas.com> wrote:

> When I edit the x86_64 Makefile to -fno-unit-at-a-time, bootup panics
> on 0xCCs in IRQ0x3e_interrupt(): IRQ0x20_interrupt etc. have got linked
> into .data.percpu.  Perhaps there are other ways of triggering that:
> specify ".text" in the BUILD_IRQ() macro for safety.
> 
> Signed-off-by: Hugh Dickins <hugh@veritas.com>

applied to tip/x86/urgent, thanks Hugh.

> I've been using -fno-unit-at-a-time (to lessen inlining, for easier 
> debugging) for a long time, but never saw this until Mike's percpu 
> mods came in: I mention this so you're on the lookout, just in case 
> other things are more likely to go into the wrong section now.  (I did 
> give Mike a private headsup on this a couple of weeks ago, in case it 
> helped with problems he was having with percpu, but in fact it didn't 
> help.)

Should we perhaps enable this automatically on CONFIG_FRAME_POINTER=y 
builds? Although a separate, default-off config option might be better, 
i'd not be surprised if there were more regressions in this area, it's a 
seldom used build vector.

	Ingo

  parent reply	other threads:[~2008-07-24 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 17:41 [PATCH] x86: BUILD_IRQ say .text to avoid .data.percpu Hugh Dickins
2008-07-21 23:25 ` Mike Travis
2008-07-22  3:49   ` Hugh Dickins
2008-07-24 10:44 ` Ingo Molnar [this message]
2008-07-25 18:45   ` CONFIG_FRAME_POINTER [was [PATCH] x86: BUILD_IRQ say .text] Hugh Dickins
2008-07-25 21:46     ` Benjamin Herrenschmidt
2008-07-26 11:02       ` Hugh Dickins
2008-07-26 12:36         ` Benjamin Herrenschmidt
2008-07-28 13:52           ` Gabriel Paubert
2008-07-28 14:41     ` Ingo Molnar
2008-07-28 14:54       ` Hugh Dickins

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=20080724104459.GI28817@elte.hu \
    --to=mingo@elte.hu \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=travis@sgi.com \
    --cc=x86@kernel.org \
    /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