linux-kernel - Re: [PATCH v5 1/6] perf tools: Derive trigger class from auxtrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 20 Apr 2016 22:20:23 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Wang Nan <wangnan0@...wei.com>
Cc:	acme@...nel.org, jolsa@...hat.com, linux-kernel@...r.kernel.org,
	pi3orama@....com, Adrian Hunter <adrian.hunter@...el.com>,
	He Kuang <hekuang@...wei.com>, Jiri Olsa <jolsa@...nel.org>,
	Masami Hiramatsu <mhiramat@...nel.org>,
	Zefan Li <lizefan@...wei.com>
Subject: Re: [PATCH v5 1/6] perf tools: Derive trigger class from
 auxtrace_snapshot

Hello,

On Mon, Apr 18, 2016 at 02:55:27PM +0000, Wang Nan wrote:
> Use 'trigger' to model operations which need to be executed when
> an event (a signal, for example) is observed.
> 
> States and transits:
> 
>  OFF--(on)--> READY --(toggle)--> TOGGLED
>                 ^                    |
>                 |                 (ready)
>                 |                    |
>                  \__________________/
> 
> is_toggled and is_ready are two key functions to query the state of
> a trigger. is_toggled means the event already happen; is_ready means the
> trigger is waiting for the event.

Not sure 'toggle' is the right word in this case.  Maybe 'set/reset'
or 'ready/hit' can be used, if each operation is one-way.  But this is
not a big deal anyway.

Btw why not split this patch into two parts - introducing trigger
logic and replacing snapshot code with the trigger?


> 
> Signed-off-by: Wang Nan <wangnan0@...wei.com>
> Cc: Adrian Hunter <adrian.hunter@...el.com>
> Cc: He Kuang <hekuang@...wei.com>
> Cc: Jiri Olsa <jolsa@...nel.org>
> Cc: Masami Hiramatsu <mhiramat@...nel.org>
> Cc: Namhyung Kim <namhyung@...nel.org>
> Cc: Zefan Li <lizefan@...wei.com>
> Cc: pi3orama@....com
> ---

[SNIP]
> +#define __TRIGGER_VAR(n) n##_state
> +#define __DEF_TRIGGER_VOID_FUNC(n, op)	\
> +static inline void n##_##op(void) {trigger_##op(&__TRIGGER_VAR(n)); }
> +#define __DEF_TRIGGER_BOOL_FUNC(n, op)	\
> +static inline bool n##_##op(void) {return trigger_##op(&__TRIGGER_VAR(n)); }
> +
> +#define DEFINE_TRIGGER(n)					\
> +struct trigger n##_state = {.state = TRIGGER_OFF, .name = #n};	\
> +__DEF_TRIGGER_VOID_FUNC(n, on)					\
> +__DEF_TRIGGER_VOID_FUNC(n, ready)				\
> +__DEF_TRIGGER_VOID_FUNC(n, toggle)				\
> +__DEF_TRIGGER_VOID_FUNC(n, off)					\
> +__DEF_TRIGGER_VOID_FUNC(n, error)				\
> +__DEF_TRIGGER_BOOL_FUNC(n, is_ready)				\
> +__DEF_TRIGGER_BOOL_FUNC(n, is_toggled)				\
> +__DEF_TRIGGER_BOOL_FUNC(n, is_error)

Why did you define all functions for each trigger variable?  Wouldn't
it be better using generic trigger code and passing the trigger instead?

Thanks,
Namhyung