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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131106060132.GB24044@gmail.com>
Date:	Wed, 6 Nov 2013 07:01:32 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Davidlohr Bueso <davidlohr@...com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Hugh Dickins <hughd@...gle.com>,
	Michel Lespinasse <walken@...gle.com>,
	Mel Gorman <mgorman@...e.de>, Rik van Riel <riel@...hat.com>,
	Guan Xuetao <gxt@...c.pku.edu.cn>, aswin@...com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	David Ahern <dsahern@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH] mm: cache largest vma


* Jiri Olsa <jolsa@...hat.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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ