From: Luca Falavigna <dktrkranz@gmail.com>
To: Jeff Sipek <jeffpc@optonline.net>
Cc: Andi Kleen <ak@suse.de>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: Re: [PATCH v2][TRIVIAL] Allocate kprobe_table at runtime
Date: Mon, 27 Jun 2005 19:52:32 +0000 [thread overview]
Message-ID: <42C05900.5050202@gmail.com> (raw)
In-Reply-To: <20050627130139.GD22311@optonline.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I agree that BSS is good enough.
Alternatively, you can implement dynamic allocation of each element of
kprobe_table in register_kprobe function. You will be able to free them by
calling unregister_kprobe function later on.
Regards,
- --
Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQEVAwUBQsBY/8zkDT3RfMB6AQJBGQf+PUMdOIpAfq4Q5lI77P7uSx1vdq2905Dp
UwowzJpBLhQoZWI94xmhp7zx2unu5IqKBoXl62sjqOLgT9/K417ReEKFKfN3SSex
shtulBOFxHfimNZX1mYhtmgJxKMU3jb3jyjXQg4oufL15Khl5PqkIxWewcVGB8LB
bciH1242moxl7jKmEJXqm8IU4ZezOpfRoBYnvaxVrr1zL/zQzUgISgBfb2GkYpSP
ErXg+w8ggUJ/TDlkZyGjT1OmjhLmb1ekYxzUE/K+dYnP5GGC/sGx5t/YgLxiKXjL
nfNM7oF8qP43eArFmbQlUpMAXpkCWOGr7v5Ifcq8hJRfo99B9GL5uA==
=fBGJ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-06-28 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050626183049.GA22898@optonline.net.suse.lists.linux.kernel>
[not found] ` <20050627055150.GA10659@in.ibm.com.suse.lists.linux.kernel>
2005-06-27 6:14 ` [PATCH][TRIVIAL] Allocate kprobe_table at runtime Andi Kleen
2005-06-27 13:01 ` [PATCH v2][TRIVIAL] " Jeff Sipek
2005-06-27 19:52 ` Luca Falavigna [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=42C05900.5050202@gmail.com \
--to=dktrkranz@gmail.com \
--cc=ak@suse.de \
--cc=jeffpc@optonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=trivial@rustcorp.com.au \
/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