All of lore.kernel.org
 help / color / mirror / Atom feed
From: jmerkey@wolfmountaingroup.com
To: jmerkey@wolfmountaingroup.com
Cc: "Ingo Molnar" <mingo@elte.hu>,
	jmerkey@wolfmountaingroup.com,
	"Pekka Enberg" <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org, jason.wessel@windriver.com
Subject: Re: [PATCH 2.6.27-rc3 26/29] mdb: export task_curr
Date: Fri, 15 Aug 2008 11:14:03 -0600 (MDT)	[thread overview]
Message-ID: <1734.69.2.248.210.1218820443.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <1151.69.2.248.210.1218817564.squirrel@webmail.wolfmountaingroup.com>

>>
>> * jmerkey@wolfmountaingroup.com <jmerkey@wolfmountaingroup.com> wrote:
>>
>>> >
>>> > * jmerkey@wolfmountaingroup.com <jmerkey@wolfmountaingroup.com>
>>> wrote:
>>> >
>>> >> > On Thu, Aug 14, 2008 at 9:14 AM,  <jmerkey@wolfmountaingroup.com>
>>> >> wrote:
>>> >> >> export the task_curr function to the module based kernel debugger
>>> to
>>> >> >> enable
>>> >> >> process back tracing and state display.
>>> >> >>
>>> >> >> Signed-off-by: Jeffrey Vernon Merkey
>>> (jmerkey@wolfmountaingroup.com)
>>> >> >>
>>> >> >> --- a/kernel/sched.c    2008-08-13 14:22:32.000000000 -0600
>>> >> >> +++ b/kernel/sched.c    2008-08-13 11:56:03.000000000 -0600
>>> >> >> @@ -1736,6 +1736,9 @@
>>> >> >>  {
>>> >> >>        return cpu_curr(task_cpu(p)) == p;
>>> >> >>  }
>>> >> >> +#if defined(CONFIG_MDB_MODULE)
>>> >> >> +EXPORT_SYMBOL_GPL(task_curr);
>>> >> >> +#endif
>>> >> >
>>> >> > We usually don't export symbols conditionally, especially in core
>>> >> kernel
>>> >> > code.
>>> >> >
>>> >>
>>> >> Well,then please suggest how a kernel debugger can be module based
>>> and
>>> >> still be able to get this information some other way that's generic
>>> >> and minimal impact.
>>> >
>>> > FYI, there's a built-in kernel debugger in the upstream kernel
>>> already:
>>> > kernel/kgdb.c - and it does not need that export.
>>> >
>>> > So if you are interested in kernel debuggers i'd suggest to work with
>>> > the KGDB folks to extend it with whatever feature-set is missing.
>>> >
>>> > They are friendly, very easy to work with and are open to the
>>> > thousands-of-years-old scientific method of not duplicating effort,
>>> > working together, going forward gradually, etc.
>>> >
>>> > 	Ingo
>>> >
>>>
>>> Sorry, but I have my own path and direction, [...]
>>
>> doing things alone is your unalienable personal right, and since thus
>> you apparently didnt intend your patch to be included in the Linux
>> kernel that's as far as my interest in this as a maintainer goes.
>>
>> Thanks,
>>
>> 	Ingo
>>


I removed the export from this file and will resubmit the patch series. 
This will remove you from the decision list for this patch series.  What
other files do you claim to maintain so I can make certain remove them
from my patches?

I can get the variable some other way.

:-)

Thanks

Jeff





  reply	other threads:[~2008-08-15 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14  6:14 [PATCH 2.6.27-rc3 26/29] mdb: export task_curr jmerkey
2008-08-14  8:39 ` Pekka Enberg
2008-08-14 14:35   ` jmerkey
2008-08-14 15:05     ` Johannes Weiner
2008-08-14 14:49       ` jmerkey
2008-08-15 12:25     ` Ingo Molnar
2008-08-15 15:58       ` jmerkey
2008-08-15 16:39         ` Ingo Molnar
2008-08-15 16:26           ` jmerkey
2008-08-15 17:14             ` jmerkey [this message]
2008-08-15 16:13       ` jmerkey

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=1734.69.2.248.210.1218820443.squirrel@webmail.wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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.