linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org,
	Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Subject: Re: [PATCH 7/7] kernel-shark-qt: Add a plugin for sched events.
Date: Thu, 30 Aug 2018 14:49:40 +0300	[thread overview]
Message-ID: <41c7443b-036b-4257-a7f5-5e17e06debc2@gmail.com> (raw)
In-Reply-To: <5df48f08-af41-ed48-9227-d36528b52734@gmail.com>



On 30.08.2018 14:48, Yordan Karadzhov (VMware) wrote:
> 
> 
> On 30.08.2018 05:43, Steven Rostedt wrote:
>>>   set(PLUGIN_LIST "")
>>> +ADD_PLUGIN(NAME sched_events
>>> +           SOURCE sched_events.c SchedEvents.cpp)

I guess I have to change the name of the function from ADD_PLUGIN to 
BUILD_PLUGIN, because this is what it actually does.

Thanks!
Yordan

>> Do all plugins need to be added like this? Is there a way to make a
>> default rule for a "plugin" directory, that we add source files of this
>> type and have them created automatically just by adding in the source
>> files?
>>
>>> +
>>> +# list(APPEND PLUGIN_LIST "sched_events default") # This plugin will 
>>> be loaded by default
>>> +list(APPEND PLUGIN_LIST "sched_events") # This plugin isn't loaded 
>>> by default
>>> +
> 
> Yes, in order to add a plugin you have to do two things. First you have 
> call the ADD_PLUGIN function. Second, you have to add the plugin to the 
> list of plugin names, specifying if the plugin will be loaded by default.
> 
> It is possible to make it working just by adding the source files but I 
> am not a big fan of this approach. If we go this way we have to enforce 
> very strict rules for naming the files. Note that this plugin is build 
> form one .c file and one .cpp file, however the plugin for renamed 
> threads will have only one .c file. And in the future we may have 
> plugins having .py files.
> 
> Thanks!
> Yordan
> 
> 
>>> +install(TARGETS sched_events
>>> +        LIBRARY DESTINATION/usr/local/lib/kshark/)
>>> +

  reply	other threads:[~2018-08-30 15:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 16:42 [PATCH 0/7] The infrastructure for plugins used by the Qt-based Yordan Karadzhov (VMware)
2018-08-29 16:42 ` [PATCH 1/7] kernel-shark-qt: Add plugin infrastructure to be used by the Qt-baset KS Yordan Karadzhov (VMware)
2018-08-29 20:12   ` Steven Rostedt
2018-08-29 20:17   ` Steven Rostedt
2018-08-29 20:32   ` Steven Rostedt
2018-08-30 11:45     ` Yordan Karadzhov (VMware)
2018-08-30 16:17       ` Steven Rostedt
2018-08-29 16:42 ` [PATCH 2/7] kernel-shark-qt: Add Plugin event handlers to session Yordan Karadzhov (VMware)
2018-08-30  2:08   ` Steven Rostedt
2018-08-29 16:42 ` [PATCH 3/7] kernel-shark-qt: Add C++/C conversion for args of a plugin draw function Yordan Karadzhov (VMware)
2018-08-29 16:42 ` [PATCH 4/7] kernel-shark-qt: Make kshark_read_at() non-static Yordan Karadzhov (VMware)
2018-08-29 16:42 ` [PATCH 5/7] kernel-shark-qt: Add src/plugins dir. to hold the source code of the plugins Yordan Karadzhov (VMware)
2018-08-29 16:42 ` [PATCH 6/7] kernel-shark-qt: Tell Doxygen to enter ../src/plugins/ Yordan Karadzhov (VMware)
2018-08-29 16:42 ` [PATCH 7/7] kernel-shark-qt: Add a plugin for sched events Yordan Karadzhov (VMware)
2018-08-30  2:43   ` Steven Rostedt
2018-08-30 11:48     ` Yordan Karadzhov (VMware)
2018-08-30 11:49       ` Yordan Karadzhov (VMware) [this message]
2018-08-30 14:12       ` Steven Rostedt
2018-08-30 11:51     ` Yordan Karadzhov (VMware)
2018-08-30 14:13       ` Steven Rostedt
2018-08-30 14:50     ` Steven Rostedt
2018-08-30 17:38   ` Steven Rostedt
2018-08-29 16:49 ` [PATCH 0/7] Add infrastructure for plugins Yordan Karadzhov (VMware)
  -- strict thread matches above, loose matches on Subject: below --
2018-09-04 15:52 Yordan Karadzhov (VMware)
2018-09-04 15:52 ` [PATCH 7/7] kernel-shark-qt: Add a plugin for sched events Yordan Karadzhov (VMware)

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=41c7443b-036b-4257-a7f5-5e17e06debc2@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tz.stoyanov@gmail.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;
as well as URLs for NNTP newsgroup(s).