From: Yordan Karadzhov <ykaradzhov@vmware.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 2/4] kernel-shark-qt: Add KernalShark Utils
Date: Wed, 10 Oct 2018 18:25:52 +0300 [thread overview]
Message-ID: <2a8bf041-2fe6-9464-4795-f06b4bdad0e2@vmware.com> (raw)
In-Reply-To: <20181010112214.320b61fc@gandalf.local.home>
On 10.10.2018 18:22, Steven Rostedt wrote:
> On Wed, 10 Oct 2018 17:12:40 +0300
> Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
>
>> On 9.10.2018 19:34, Steven Rostedt wrote:
>>>> + if (!kshark_instance(&kshark_ctx))
>>>> + return;
>>>> +
>>>> + switch (filterId) {
>>>> + case KS_SHOW_EVENT_FILTER:
>>>> + case KS_HIDE_EVENT_FILTER:
>>>> + kshark_filter_clear(kshark_ctx, KS_SHOW_EVENT_FILTER);
>>>> + kshark_filter_clear(kshark_ctx, KS_HIDE_EVENT_FILTER);
>>> Hmm, I'm curious to why you clear both SHOW/HIDE filters if the
>>> filterId is one of SHOW or HIDE?
>>>
>>> Perhaps a comment should be here explaining it too.
>>>
>>>
>>
>> This enforces that we cannot have both SHOW and HIDE filters being set.
>> I think that, having SHOW and HIDE filters set in the same time can be
>> useful in very limited number of cases. On the other hand this is an
>> easy way to confuse yourself.
>>
>> Note that this restriction is at the level of the GUI code. The C API
>> allows for having both SHOW and HIDE filters in the same time.
>>
>
> Actually, there are real uses to do both. You may want to show a
> specific kind of event, and then you may want to filter a subset of
> that event.
>
But if you want to filter a subset of one event you have to use the
advanced filtering, while the logic in the "switch" is only for the "Id
filters".
Thanks!
Yordan
> -- Steve
>
next prev parent reply other threads:[~2018-10-10 22:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 15:16 [PATCH 0/4] Add basic components to be used by the Qt GUI Yordan Karadzhov
2018-10-08 15:16 ` [PATCH 1/4] kernel-shark-qt: Add Qt as a third party dependency Yordan Karadzhov
2018-10-08 15:16 ` [PATCH 2/4] kernel-shark-qt: Add KernalShark Utils Yordan Karadzhov
2018-10-09 16:34 ` Steven Rostedt
2018-10-10 14:12 ` Yordan Karadzhov
2018-10-10 15:22 ` Steven Rostedt
2018-10-10 15:25 ` Yordan Karadzhov [this message]
2018-10-10 19:02 ` Steven Rostedt
2018-10-10 15:27 ` Yordan Karadzhov
2018-10-10 15:27 ` Yordan Karadzhov
2018-10-10 19:04 ` Steven Rostedt
2018-10-08 15:16 ` [PATCH 3/4] kernel-shark-qt: Add Widgets Lib Yordan Karadzhov
2018-10-09 16:42 ` Steven Rostedt
2018-10-08 15:16 ` [PATCH 4/4] kernel-shark-qt: Add widget demo example Yordan Karadzhov
2018-10-09 16:45 ` 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=2a8bf041-2fe6-9464-4795-f06b4bdad0e2@vmware.com \
--to=ykaradzhov@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).