mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386: make BUG() expansion look like instruction
Date: Wed, 8 Nov 2006 17:41:43 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0611081733300.5025@blonde.wat.veritas.com> (raw)
In-Reply-To: <45521329.76E4.0078.0@novell.com>

On Wed, 8 Nov 2006, Jan Beulich wrote:
> This gets i386's handle_BUG() in sync with x86-64's, namely introducing
> a 'struct bug_frame' and arranging for the code generated by the BUG()
> macro to represent an instruction, so that disassembling code
> containing such constructs doesn't produce garbage anymore. The
> resulting increase of code size is marginal (1 byte per instance).

I thought we were heading towards merging Jeremy's generic-bug-*
(with file and line in another section), in -mm for a while now?

Hugh

  reply	other threads:[~2006-11-08 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:26 Jan Beulich
2006-11-08 17:41 ` Hugh Dickins [this message]
2006-11-08 20:43   ` Jeremy Fitzhardinge

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=Pine.LNX.4.64.0611081733300.5025@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=jbeulich@novell.com \
    --cc=jeremy@goop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®