public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20120424 release(doc update)[1/3]code
Date: Wed, 25 Apr 2012 02:49:19 -0700	[thread overview]
Message-ID: <m2mx60m99c.fsf@firstfloor.org> (raw)
In-Reply-To: <4F96A881.7050507@gmail.com> (Hui Zhu's message of "Tue, 24 Apr 2012 21:20:01 +0800")

Hui Zhu <teawater@gmail.com> writes:

Could you please split it down further. a 9kLOC patch is pretty daunting.

>From a quick glance over some focus on simplication would be good: no
own allocators (kernel has enough), no own types (that would remove
asm), remove optional facilities like the private ring buffer. Some
obsolete code like using semaphores vs mutexes. The variable list looks
overcomplicated, just use an array? Generally too many macros I would
say, try using inlines or removing them.  

Do you have any rarely used optional features that could be left out a
version 1? If yes do that.  I'm sure with some effort the 9kLOC could be
much less. A patch half the size would be much easier to merge.

There are some things that checkpatch will likely warn about.

It would be good if you could describe the use case a bit better:
this is for the kernel only or also user applications?

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2012-04-25  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 13:20 KGTP (Linux Kernel debugger and tracer) 20120424 release(doc update)[1/3]code Hui Zhu
2012-04-25  9:49 ` Andi Kleen [this message]
2012-05-04  0:23   ` Hui Zhu

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=m2mx60m99c.fsf@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teawater@gmail.com \
    /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