DESCRIPTION

TMF: Add an interface for strings regarding a session configuration

Creation of the lttng2.core.session package with the strings that will be used
for both session configuration generation and LTTng analysis requirements.
We also externalized the package for the kernel and ust plugin.

Change-Id: If51a4805064ed701a2bbf31a7f327406410f71a6
Signed-off-by: Bailey Galloway xxx@xxx.xxx


COMMENTS

author: Bailey Galloway
date: 2014-03-20 02:00:31.000000000

Uploaded patch set 2.

-------------------------------------
author: Brenden Conley
date: 2014-03-20 02:00:36.000000000

Patch Set 2:

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/6047/

-------------------------------------
author: Brenden Conley
date: 2014-03-20 02:46:01.000000000

Patch Set 2: Verified+1

Build Successful 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/6047/ : SUCCESS

-------------------------------------
author: Ricky Reeves
date: 2014-03-21 11:15:28.000000000

Patch Set 2: Code-Review-1

(1 comment)

Line:98, lttng/org.eclipse.linuxtools.lttng2.core/src/org/eclipse/linuxtools/lttng2/core/session/SessionConfigStrings.java -> About the default values. Right now we decided to not pass default values for the control view. Instead we let the remote side (tracer) decide the default values. The reason is that from one release to another the default values changes. Also, different Linux distributions might have different default values. For example, in Ubuntu the default channel size for UST is 4MB (I think), but if you install LTTng from source code its different). Anther example, LTTng 2.2 the default buffer type for UST is per pid but in LTTng 2.3 it's per UID.

So, when the user doesn't specify any values for a particular configuration parameter this parameter won't be passed by the control view and the tracer will decide. I think the same approach should be taken for the XML profile.

-------------------------------------
