All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Falavigna <dktrkranz@gmail.com>
To: Greg KH <greg@kroah.com>, Nathan Lynch <nathanl@austin.ibm.com>
Cc: vamsi_krishna@in.ibm.com, prasanna@in.ibm.com,
	suparna@in.ibm.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Kprobes /proc entry
Date: Wed, 12 Jan 2005 01:09:50 +0100	[thread overview]
Message-ID: <41E46ACE.2040101@gmail.com> (raw)
In-Reply-To: <20050111213400.GB18422@kroah.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greg KH ha scritto:
> On Tue, Jan 11, 2005 at 03:31:17PM -0600, Nathan Lynch wrote:
> 
>>On Mon, 2005-01-10 at 12:14, Greg KH wrote:
>>
>>>On Mon, Jan 10, 2005 at 05:25:38PM +0100, Luca Falavigna wrote:
>>>
>>>>This simple patch adds a new file in /proc, listing every kprobe which
>>>>is currently registered in the kernel. This patch is checked against
>>>>kernel 2.6.10
>>>
>>>No, please do not add extra /proc files to the kernel.  This belongs in
>>>/sys, as it has _nothing_ to do with processes.
>>
>>Wouldn't this sort of thing be a good candidate for debugfs?  If you're
>>messing with kprobes, then aren't you by definition doing kernel
>>debugging? :)
> 
> 
> That's an even better idea, I like it.
> 
> greg k-h
> 

Good, I'll work on it ASAP.
Thank you for your suggestions!

					Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQEVAwUBQeRqzRZrwl7j21nOAQJrFQf/RnBUDTsju6LLcYRdM6RYiyrnydTBJWtw
Q3MuNE9S/kiwmFpCJjshV9tazJ+dA29pxuqt+Wg2aGkqSSVgq8KuuF1uSLIlaatM
n0ZSZ/tnOEJoQtlI32azik+PYVQkHHcr2HMN5ruThRO3uCJfHuYZEGEGaUkZQRa+
ORGrVgXSoLVCQmenIOaXHDW1UNOdKb1IgyU4HBpjL8zVUWOLTB7jbtxghC5rDgHP
BV9AYP0GaeIb7Xy5l/bcfngU+teKE75ht+ew5xzX3Ee0Sz9G5a5YVvWJTecHSyeq
id4WK0etFHp8qufX/gcGr0uTY8gpxF8GCzwcU8KCr32Y6vvLlVKzxQ==
=BXBj
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-01-12  0:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 16:25 [PATCH] Kprobes /proc entry Luca Falavigna
2005-01-10 18:14 ` Greg KH
2005-01-11 21:31   ` Nathan Lynch
2005-01-11 21:34     ` Greg KH
2005-01-12  0:09       ` Luca Falavigna [this message]
2005-01-12  6:35         ` Prasanna S Panchamukhi
2005-01-12  9:49           ` Prasanna S Panchamukhi
2005-01-13 23:20       ` Luca Falavigna
2005-01-13 23:34         ` Greg KH
2005-01-17 16:58           ` Luca Falavigna
2005-01-18  6:44             ` Greg KH
2005-01-20 14:13               ` Luca Falavigna
2005-01-14  0:22         ` Stephen Hemminger

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=41E46ACE.2040101@gmail.com \
    --to=dktrkranz@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=prasanna@in.ibm.com \
    --cc=suparna@in.ibm.com \
    --cc=vamsi_krishna@in.ibm.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 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.