From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kgdb:unify x86-kgdb
Date: Thu, 17 Jan 2008 15:43:15 +0100 [thread overview]
Message-ID: <478F6983.5010707@siemens.com> (raw)
In-Reply-To: <478F67BF.4090409@windriver.com>
Jason Wessel wrote:
> Jan Kiszka wrote:
>> diff -up arch/x86/kernel/kgdb_32.c arch/x86/kernel/kgdb_64.c
>>
>> screamed for unification. Here it is.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> ---
>> arch/x86/kernel/Makefile_32 | 2
>> arch/x86/kernel/Makefile_64 | 2
>> arch/x86/kernel/kgdb.c | 561 ++++++++++++++++++++++++++++++++++++++++++++
>> arch/x86/kernel/kgdb_32.c | 414 --------------------------------
>> arch/x86/kernel/kgdb_64.c | 495 --------------------------------------
>> 5 files changed, 563 insertions(+), 911 deletions(-)
>>
> FYI this is already done in the head branch for kgdb which is going into
> the -mm tree. You will see the new patch set in the 2.6.25-rcX series.
>
> There is now a single x86-lite.patch which contains a number of other
> modifications to the core-lite.patch to make use of
> probe_kernel_address() and a new function probe_kernel_write(). Also
> the die hooks for the "no context" memory faults were removed.
Hmm, is this any kind of patch I should have seen in your kernel.org
git? Which branch?
Jan
next prev parent reply other threads:[~2008-01-17 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 14:32 [PATCH] kgdb:unify x86-kgdb Jan Kiszka
2008-01-17 14:35 ` Jason Wessel
2008-01-17 14:43 ` Jan Kiszka [this message]
2008-01-17 23:27 ` Jason Wessel
2008-01-18 9:10 ` Jan Kiszka
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=478F6983.5010707@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=jason.wessel@windriver.com \
--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.