Perf - Remove support for perf.data as converted CTF files and rename appropriately (#119)

* Perf - Remove support for perf.data as CTF files and rename appropiately. CTF (LTTng format) support never worked that well (like cpu sample stacks) and relied on conversion that was very niche. Perf would have to be optionally compiled with this conversion support and is quite rare. This will be replaced by native support of perf.data binary format in a future PR

Author: ivberg

LinuxTraceLogCapture.md

@@ -154,23 +154,6 @@ $ sudo perf report --header-only -i perf_cpu.data | grep "captured on"
 
 Place the "captured on" timestamp for example "Thu Oct 17 15:37:36 2019" in a timestamp.txt file next to the trace folder. The timestamp will be interpreted as UTC
 
-### Convert to CTF (Optional) (requires CTF enabled perf) 
-We have optional support for perf CTF conversion. It it currently NOT RECOMMENDED to use this though as you get less features (like KM/UM stacks) than perf.data.txt support which resolves callstacks on the box.
-This only supports KM symbols (for now) supplied by kallsyms. Microsoft-Linux-Perf-Tools support for the perf CTF trace is experimental given lack of UM symbols
-
-```bash
-$ perf data convert -i perf_cpu.data --all --to-ctf ./perf_cpu.data-ctf
-```
-
-You will need the perf file in converted CTF format which you can do with a custom compiled perf (unless some distro compiled the support in). [Custom build instructions here](https://stackoverflow.com/questions/43576997/building-perf-with-babeltrace-for-perf-to-ctf-conversion)
-
-## Save Kernel Symbols (Optional) (for use with CTF enabled perf)
-This is only needed for a perf CTF trace
-
-```bash
-$ sudo cat /proc/kallsyms > kallsyms
-```
-
 # Transferring the files to Windows UI (optional)
 You then need to transfer the perf files to a Windows box where WPA runs. The most important file is perf.data.txt
 
@@ -180,12 +163,10 @@ $ sudo chmod 777 -R perf*
 
 - Copy files from Linux to Windows box with WinSCP/SCP OR 
 ```bash
-$ tar -czvf perf_cpu-ctf.tar.gz perf*
+$ tar -czvf perf_cpu.tar.gz perf*
 ```
 - (Optional if you want absolute timestamps) Place timestamp.txt next to perf.data.txt
 - Open perf.data.txt with WPA
-- For the perf CTF file (optional) On Windows, Zip the folder up and rename to .ctf extension. E.g. perf_cpu-ctf.ctf (which is really a .zip file)
-  - CTF (Optional) Kallsyms needs to be on your Desktop
 
 
 # Presentations

Microsoft-Perf-Tools-Linux-Android.sln

@@ -11,9 +11,7 @@ Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "LTTngDataExtensions", "LTTn
 EndProject
 Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "CtfUnitTest", "CtfUnitTest\CtfUnitTest.csproj", "{FC2236A8-FBE7-43BC-86A1-CBC364DFDF91}"
 EndProject
-Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "PerfCds", "PerfCds\PerfCds.csproj", "{DF90DB4D-93B8-498F-8DA9-557495BBFCB6}"
-EndProject
-Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "PerfDataExtensions", "PerfDataExtensions\PerfDataExtensions.csproj", "{B381F72E-335C-4842-9DB2-615D5C18A943}"
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "PerfDataTxtExtension", "PerfDataTxtExtension\PerfDataTxtExtension.csproj", "{B381F72E-335C-4842-9DB2-615D5C18A943}"
 EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "LinuxLogParsers", "LinuxLogParsers", "{9B2D4167-1CC7-4D8B-A01C-E9919E809A0A}"
 EndProject
@@ -97,10 +95,6 @@ Global
 		{FC2236A8-FBE7-43BC-86A1-CBC364DFDF91}.Debug|Any CPU.Build.0 = Debug|Any CPU
 		{FC2236A8-FBE7-43BC-86A1-CBC364DFDF91}.Release|Any CPU.ActiveCfg = Release|Any CPU
 		{FC2236A8-FBE7-43BC-86A1-CBC364DFDF91}.Release|Any CPU.Build.0 = Release|Any CPU
-		{DF90DB4D-93B8-498F-8DA9-557495BBFCB6}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
-		{DF90DB4D-93B8-498F-8DA9-557495BBFCB6}.Debug|Any CPU.Build.0 = Debug|Any CPU
-		{DF90DB4D-93B8-498F-8DA9-557495BBFCB6}.Release|Any CPU.ActiveCfg = Release|Any CPU
-		{DF90DB4D-93B8-498F-8DA9-557495BBFCB6}.Release|Any CPU.Build.0 = Release|Any CPU
 		{B381F72E-335C-4842-9DB2-615D5C18A943}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
 		{B381F72E-335C-4842-9DB2-615D5C18A943}.Debug|Any CPU.Build.0 = Debug|Any CPU
 		{B381F72E-335C-4842-9DB2-615D5C18A943}.Release|Any CPU.ActiveCfg = Release|Any CPU