From: Jeff Sipek <jeffpc@optonline.net>
To: Andi Kleen <ak@suse.de>
Cc: Prasanna S Panchamukhi <prasanna@in.ibm.com>,
linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: [PATCH v2][TRIVIAL] Allocate kprobe_table at runtime
Date: Mon, 27 Jun 2005 09:01:39 -0400 [thread overview]
Message-ID: <20050627130139.GD22311@optonline.net> (raw)
In-Reply-To: <p737jggwcln.fsf@verdi.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
On Mon, Jun 27, 2005 at 08:14:12AM +0200, Andi Kleen wrote:
> Prasanna S Panchamukhi <prasanna@in.ibm.com> writes:
>
> > Jeff,
> >
> > On Sun, Jun 26, 2005 at 06:37:29PM +0000, Jeff Sipek wrote:
> > > Allocates kprobe_table at runtime.
> > > - /* FIXME allocate the probe table, currently defined statically */
> > > + kprobe_table = kmalloc(sizeof(struct hlist_head)*KPROBE_TABLE_SIZE, GFP_ATOMIC);
> >
> > Memory allocation using GFP_KERNEL has more chances of success as compared to
> > GFP_ATOMIC. Why can't we use GFP_KERNEL here?
>
> I don't see any sense in the change anyways. Just using BSS
> should be fine.
>
> Jeff, when you submit a patch you should add a small blurb
> describing why you think it is a good idea.
That patch was somewhat impulsive...I was looking at some code and saw a
FIXME that required minimal work. I agree that BSS is good enough.
Patch below removes the FIXME notice.
Pick one ;-) (Patch Monkey is CC'd).
Jeff.
Remove useless FIXME.
Signed-off-by: Josef "Jeff" Sipek
diff --git a/kernel/kprobes.c b/kernel/kprobes.c
--- a/kernel/kprobes.c
+++ b/kernel/kprobes.c
@@ -261,7 +261,6 @@ static int __init init_kprobes(void)
{
int i, err = 0;
- /* FIXME allocate the probe table, currently defined statically */
/* initialize all list heads */
for (i = 0; i < KPROBE_TABLE_SIZE; i++)
INIT_HLIST_HEAD(&kprobe_table[i]);
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-27 14:51 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] " Andi Kleen
2005-06-27 13:01 ` Jeff Sipek [this message]
2005-06-27 19:52 ` [PATCH v2][TRIVIAL] " Luca Falavigna
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=20050627130139.GD22311@optonline.net \
--to=jeffpc@optonline.net \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®