From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
hpa@zytor.com, mingo@redhat.com, torvalds@linux-foundation.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-tip-commits@vger.kernel.org,
systemtap-ml <systemtap@sources.redhat.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Jim Keniston <jkenisto@us.ibm.com>
Subject: Re: [tip:x86/mm] x86, mm, kprobes: fault.c, simplify notify_page_fault()
Date: Mon, 23 Feb 2009 11:21:50 -0500 [thread overview]
Message-ID: <49A2CD1E.60606@redhat.com> (raw)
In-Reply-To: <20090222093109.GE6964@elte.hu>
Hi Ingo,
Ingo Molnar wrote:
> another very small thing, while we are discussing kprobes:
>
> I always found that the __kprobes annotation is very confusingly
> euphemistic: what those annotations really mean is not
> 'kprobes', but 'no kprobes'.
As far as I know, __kprobes originally means 'this function will be
called from kprobes'. However, now many functions are tagged as
__kprobes, it might be confusingly.
> So how about renaming __kprobes to __nokprobes, similar to how
> we have the notrace attribute?
Would you mean that will include changing section name of
'.text.kprobes'? That's what I mind.
> We have about 350 __kprobes annotations in the kernel, so
> renaming it now would not be practical - but any objections
> against me sending Linus a rename patch somewhere late in the
> next merge window that just does this rename?
Just renaming __kprobes to __nokprobes seems good for me.
Thank you!
> [ likewise, i'll rename notrace to __notrace to make it visually
> less intrusive to the return value type. There's a lot less
> such annotations in the kernel. ]
>
> Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-02-23 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-b18018126f422f5b706fd750373425e10e84b486@kernel.org>
2009-02-20 23:09 ` [tip:x86/mm] x86, mm, kprobes: fault.c, simplify notify_page_fault() Masami Hiramatsu
2009-02-22 9:31 ` Ingo Molnar
2009-02-23 16:21 ` Masami Hiramatsu [this message]
2009-02-23 18:46 ` Ananth N Mavinakayanahalli
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=49A2CD1E.60606@redhat.com \
--to=mhiramat@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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