All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@muc.de>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
Date: Thu, 28 Sep 2006 03:30:12 -0700	[thread overview]
Message-ID: <451BA434.9020409@goop.org> (raw)
In-Reply-To: <20060928101555.GA99906@muc.de>

Andi Kleen wrote:
> But no out of line section. So overall it's smaller, although the cache footprint
> is 2 bytes larger. But then is 2 bytes larger really an issue? We don't have
> _that_ many BUGs anyways.
>   

I think the out of line section is a feature; no point in crufting up 
the icache with BUG gunk, especially since a number of them are on 
fairly hot paths.

> I'll port the x86-64 way over to i386

It's neat, and it would solve my immediate problem, but I think my way 
is actually better.

    J

  reply	other threads:[~2006-09-28 10:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  6:00 [PATCH] Put the BUG __FILE__ and __LINE__ info out of line Jeremy Fitzhardinge
2006-09-28  6:35 ` Andrew Morton
2006-09-28  6:49   ` Jeremy Fitzhardinge
2006-09-28  7:00     ` Andrew Morton
2006-09-28  7:17       ` Andi Kleen
2006-09-28  7:26         ` Andrew Morton
2006-09-28 10:15           ` Andi Kleen
2006-09-28 10:30             ` Jeremy Fitzhardinge [this message]
2006-09-28 10:38               ` Andi Kleen
2006-09-28 15:30                 ` Hugh Dickins
2006-09-28 19:44                   ` Andi Kleen
2006-09-28 10:27       ` Jeremy Fitzhardinge
2006-09-28 16:18         ` Andrew Morton
2006-09-28 16:32           ` Jeremy Fitzhardinge
2006-09-28  7:16 ` Andi Kleen

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=451BA434.9020409@goop.org \
    --to=jeremy@goop.org \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.