* Jiri Olsa <jo...@redhat.com> wrote:
> > But success primarily depends on how useful the tooling UI turns out
> > to be: create a nice Slang or GTK UI for kprobes and triggers, and/or
> > turn it into a really intuitive command line UI, and people will use
> > it.
> >
> > I think annotated assembly/source output is a really nice match for
> > triggers and kprobes, so I'd suggest the Slang TUI route ...
>
> yep, current toggling command line UI is not much user friendly
>
> but perhaps we should leave it there (because it seems it wont get much
> better anyway) and focus more on Slang UI as the target one..
>
> CCing Arnaldo ;-)
Btw., I think we should do the TUI interface _before_ we can merge the
kernel changes. Frankly, 'not very user friendly' means that it's not used
(and tested) much - which begs the question: why merge the feature at all?
Making a new kernel feature usable to as many people as possible must be a
primary concern, not an afterthought.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
