From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <dahi@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Xenia Ragiadakou <burzalodowa@gmail.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Mark Brown <broonie@linaro.org>
Subject: Re: [RFC][PATCH] tracing: Replace '-' with '_' in event system names
Date: Wed, 1 Apr 2015 12:36:57 +0200 [thread overview]
Message-ID: <20150401123657.29d01802.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20150331231802.23527931@grimm.local.home>
On Tue, 31 Mar 2015 23:18:02 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> There's a change I want to make to the tracing infrastructure that may
> require TRACE_SYSTEM be a valid variable name. As '-' can not be used
> in a variable, and I found only three cases that it is a TRACE_SYSTEM
> name, I want to ask those that are responsible if it is OK to change
> them?
>
> The three systems are:
>
> #define TRACE_SYSTEM kvm-s390
> #define TRACE_SYSTEM xhci-hcd
> #define TRACE_SYSTEM intel-sst
>
>
> I want to replace the '-' with '_'. But this will have a user space
> visible affect, which is why I'm inquiring with you. If this will break
> any scripts or annoy any users that you know of, I'll need to make a
> work around (which would not be hard to do). But if I don't need to do
> that, I prefer to just use TRACE_SYSTEM as is.
>
> I'll just do the work around if there is any user space tool that you
> know of that will break with this change.
>
> The effect is that the directories in /sys/kernel/debug/tracing/events/
> will be different. That is,
>
> /sys/kernel/debug/tracing/events/kvm-s390/
>
> will become
>
> /sys/kernel/debug/tracing/events/kvm_s390/
>
> And the same for the other two. Is this a problem?
The only direct dependency for kvm-s390 I'm aware of is in
perf/tests/parse-events.c, added because parsing an event with '-' in
the name was broken.
Otherwise, I'm not aware of things that should break, excluding local
scripts and so on of course.
next prev parent reply other threads:[~2015-04-01 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 3:18 Steven Rostedt
2015-04-01 9:20 ` Xenia Ragiadakou
2015-04-01 10:36 ` Cornelia Huck [this message]
2015-04-01 17:06 ` Steven Rostedt
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=20150401123657.29d01802.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=broonie@linaro.org \
--cc=burzalodowa@gmail.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sarah.a.sharp@linux.intel.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 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®