From: Steven Rostedt <rostedt@goodmis.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-fsdevel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] afs: fix tracepoint string placement with built-in AFS
Date: Mon, 14 Jun 2021 21:17:45 -0400 [thread overview]
Message-ID: <20210614211745.6eb3d9ca@oasis.local.home> (raw)
In-Reply-To: <20210614164752.12438695a27203c8e7c9eaea@linux-foundation.org>
On Mon, 14 Jun 2021 16:47:52 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> Should/can afs_SRXCB##name##_name[] be static?
Probably.
>
>
> __tracepoint_string is very rarely used. I wonder if there's much
> point in it existing?
There's a few places that the "tracepoint_string()" couldn't be used,
and this was a workaround for those locations. Yes, it's not used much,
but what's the other solution should we use to replace it?
>
>
> kernel/rcu/tree.h does
>
> static char rcu_name[] = RCU_NAME_RAW;
> static const char *tp_rcu_varname __used __tracepoint_string = rcu_name;
>
> which is asking the compiler to place a copy of these into each
> compilation unit which includes tree.h, which probably isn't what was
> intended.
Yeah, there's a couple of duplicates. Perhaps we can move them into a C
file, and have it simply exported.
-- Steve
next prev parent reply other threads:[~2021-06-15 2:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 22:04 [PATCH] afs: fix tracepoint string placement with built-in AFS Alexey Dobriyan
2021-06-14 16:07 ` Alexey Dobriyan
2021-06-14 23:47 ` Andrew Morton
2021-06-15 1:17 ` Steven Rostedt [this message]
2021-06-15 8:19 ` David Howells
2021-06-15 8:49 ` David Howells
2021-06-15 10:58 ` David Howells
2021-06-15 15:54 ` Steven Rostedt
2021-06-17 12:04 ` David Howells
2021-06-17 13:37 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2021-06-21 20:57 [PATCH] afs: Fix " David Howells
2021-06-22 6:51 [PATCH] afs: fix " Zeng Tao
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=20210614211745.6eb3d9ca@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=paulmck@linux.vnet.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.