All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH] kgdb:unify x86-kgdb
Date: Fri, 18 Jan 2008 10:10:42 +0100	[thread overview]
Message-ID: <47906D12.9090206@siemens.com> (raw)
In-Reply-To: <478FE465.5000606@windriver.com>

Jason Wessel wrote:
> Jan Kiszka wrote:
>> 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?
>>   

Meanwhile I realized that the actual head-of-development was some branch
in the corner of kgdb's cvs on sf.net - I hope this will change in the
future... :->

> I'll be posting an update to the -mm tree soon.  Presently, I have been
> updating the x86 patch set because the x86 developers provided some
> insight as to what needed to change to gain adoption into the mainline
> kernel.
> 
> 
> See:
> http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=for_x86

Thanks, will pick it up and continue to hammer against it.

> 
> Right now the scope is only 8 patches worth.  The other archs will be
> patched in when I move the patches forward against the -mm tree.
> 
> If you or anyone else would like to help, I'll be happy to forward a
> copy of the todo list :-)

Can't promise anything beyond x86 ATM, because that's the arch our
customer asked for. But I will look around here if someone happens to
twiddle thumbs. ;)

Jan

      reply	other threads:[~2008-01-18  9:11 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
2008-01-17 23:27     ` Jason Wessel
2008-01-18  9:10       ` Jan Kiszka [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=47906D12.9090206@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --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.