Skip to content
Snippets Groups Projects
  1. Feb 20, 2019
  2. Feb 07, 2019
    • Soumen Ghosh's avatar
      lrdpv2: kill the process after QTF timeout. · 7f3c1e58
      Soumen Ghosh authored
                  kill the qtf server forcefully after completion of qtf parsing. Here if QTF processed successfuly
                  within timeout value then QTF sever will be closed gracefuly, but if it is not completed then forcefuly
                  we have to kill the qtfserver and all child processes
      
      Change-Id: Ifac67357568eb2b5b4f73159176c257fcdafa9a6
      7f3c1e58
  3. Jan 23, 2019
  4. Jan 19, 2019
  5. Jan 17, 2019
  6. Jan 16, 2019
  7. Jan 08, 2019
  8. Jan 07, 2019
  9. Dec 27, 2018
  10. Dec 21, 2018
  11. Dec 20, 2018
  12. Dec 15, 2018
  13. Dec 11, 2018
  14. Dec 06, 2018
  15. Nov 29, 2018
  16. Nov 21, 2018
  17. Nov 08, 2018
  18. Oct 30, 2018
  19. Oct 29, 2018
  20. Oct 25, 2018
  21. Oct 24, 2018
  22. Oct 23, 2018
  23. Oct 19, 2018
  24. Oct 17, 2018
    • qctecmdr Service's avatar
      Merge "lrdp-v2: setting kimage_voffset to null In case of 32bit... · 15dd9067
      qctecmdr Service authored
      Merge "lrdp-v2: setting kimage_voffset to null         In case of 32bit ramdump kimage_voffset will not be used in ramparser.         In upstream kernel 4.14 this variable got added and set to some address.         Due to that in case of 32 bit all calculation went worng. So forcefully setting to null if it is 32 bit dump"
      15dd9067
  25. Oct 11, 2018
  26. Oct 10, 2018
  27. Oct 08, 2018
    • Kumar Harsh's avatar
      ldrp_V2 : Extract IO Event & console logs from pstore · 9eba037b
      Kumar Harsh authored
      
      IO event logs such as register read/write are
      being logged into pstore. This change helps in
      extracting that data on per cpu basis into
      separate files. Also this change is extracting
      the console logs from pstore buffer since dmesg
      gets corrupted sometimes and this acts as an
      additional logging mechanism to turn to.
      
      Change-Id: I19bdef9c58d76b4b46efa39261ca2f36ae3b1a22
      Signed-off-by: default avatarKumar Harsh <harkumar@codeaurora.org>
      9eba037b
  28. Oct 05, 2018
  29. Oct 03, 2018
  30. Oct 01, 2018
  31. Sep 28, 2018
  32. Sep 25, 2018
    • Kumar Harsh's avatar
      ldrp_V2 : Support increased length in Linux banner string · a2583fc2
      Kumar Harsh authored
      
      This patch fixes the need for a hard coded value
      to specify upper limit on length of the Linux Banner.
      
      get_version() inside ramdump.py has been renamed to
      get_matched_version() to reflect the true nature of
      the function.
      
      Added a variable banner_len in get_matched_version()
      which is the length of linux_banner returned by
      gdbmi.get_value_of_string('linux_banner').
      This variable is further passed to read_cstring()
      function to specify the max limit of characters to
      be read. We are dynamically calculating the length
      using gdb to read linux banner.
      
      Change-Id: I571882a5999c26ccd8accd90b26d0149c839633b
      Signed-off-by: default avatarKumar Harsh <harkumar@codeaurora.org>
      a2583fc2
  33. Sep 24, 2018
Loading