From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org, hpa@zytor.com,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] allow bug table entries to use relative pointers (and use it on x86-64)
Date: Tue, 16 Dec 2008 18:40:48 +0100 [thread overview]
Message-ID: <20081216174048.GH11683@elte.hu> (raw)
In-Reply-To: <4947A1BB.76E4.0078.0@novell.com>
* Jan Beulich <jbeulich@novell.com> wrote:
> This allows reducing the bug table size by half. Perhaps there are
> other 64-bit architectures that could also make use of this.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> ---
> arch/x86/Kconfig | 4 ++++
> arch/x86/include/asm/bug.h | 2 +-
> include/asm-generic/bug.h | 8 ++++++++
> lib/bug.c | 19 +++++++++++++++++--
> 4 files changed, 30 insertions(+), 3 deletions(-)
applied to tip/x86/debug, thanks Jan!
Ingo
prev parent reply other threads:[~2008-12-16 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 11:40 [PATCH] allow bug table entries to use relative pointers (and use it on x86-64) Jan Beulich
2008-12-16 11:40 ` Jan Beulich
2008-12-16 17:40 ` Ingo Molnar [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=20081216174048.GH11683@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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