1. 13 1月, 2019 3 次提交
  2. 10 1月, 2019 1 次提交
  3. 29 12月, 2018 1 次提交
  4. 21 12月, 2018 1 次提交
  5. 20 12月, 2018 1 次提交
  6. 17 12月, 2018 1 次提交
  7. 13 12月, 2018 1 次提交
  8. 08 12月, 2018 1 次提交
  9. 06 12月, 2018 1 次提交
  10. 01 12月, 2018 1 次提交
  11. 27 11月, 2018 1 次提交
  12. 23 11月, 2018 1 次提交
  13. 21 11月, 2018 1 次提交
  14. 14 11月, 2018 1 次提交
  15. 04 11月, 2018 1 次提交
  16. 22 10月, 2018 1 次提交
  17. 15 10月, 2018 1 次提交
  18. 07 10月, 2018 1 次提交
  19. 30 9月, 2018 1 次提交
  20. 24 9月, 2018 1 次提交
  21. 19 9月, 2018 1 次提交
  22. 17 9月, 2018 1 次提交
  23. 13 9月, 2018 1 次提交
    • P
      tracing/Makefile: Fix handling redefinition of CC_FLAGS_FTRACE · b1f4ff74
      Paulo Zanoni 提交于
      As a Kernel developer, I make heavy use of "make targz-pkg" in order
      to locally compile and remotely install my development Kernels. The
      nice feature I rely on is that after a normal "make", "make targz-pkg"
      only generates the tarball without having to recompile everything.
      
      That was true until commit f28bc3c3 ("tracing: Handle
      CC_FLAGS_FTRACE more accurately"). After it, running "make targz-pkg"
      after "make" will recompile the whole Kernel tree, making my
      development workflow much slower.
      
      The Kernel is choosing to recompile everything because it claims the
      command line has changed. A diff of the .cmd files show a repeated
      -mfentry in one of the files. That is because "make targz-pkg" calls
      "make modules_install" and the environment is already populated with
      the exported variables, CC_FLAGS_FTRACE being one of them. Then,
      -mfentry gets duplicated because it is not protected behind an ifndef
      block, like -pg.
      
      To complicate the problem a little bit more, architectures can define
      their own version CC_FLAGS_FTRACE, so our code not only has to
      consider recursive Makefiles, but also architecture overrides.
      
      So in this patch we move CC_FLAGS_FTRACE up and unconditionally
      define it to -pg. Then we let the architecture Makefiles possibly
      override it, and finally append the extra options later. This ensures
      the variable is always fully redefined at each invocation so recursive
      Makefiles don't keep appending, and hopefully it maintains the
      intended behavior on how architectures can override the defaults..
      
      Thanks Steven Rostedt and Vasily Gorbik for the help on this
      regression.
      
      Cc: Michal Marek <michal.lkml@markovi.net>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
      Cc: linux-kbuild@vger.kernel.org
      Fixes: commit f28bc3c3 ("tracing: Handle CC_FLAGS_FTRACE more accurately")
      Acked-by: NVasily Gorbik <gor@linux.ibm.com>
      Signed-off-by: NPaulo Zanoni <paulo.r.zanoni@intel.com>
      Signed-off-by: NSteven Rostedt (VMware) <rostedt@goodmis.org>
      b1f4ff74
  24. 10 9月, 2018 1 次提交
  25. 05 9月, 2018 1 次提交
  26. 03 9月, 2018 1 次提交
  27. 31 8月, 2018 1 次提交
  28. 27 8月, 2018 1 次提交
  29. 24 8月, 2018 2 次提交
  30. 22 8月, 2018 1 次提交
  31. 21 8月, 2018 1 次提交
  32. 16 8月, 2018 3 次提交
  33. 13 8月, 2018 1 次提交
  34. 09 8月, 2018 1 次提交
  35. 07 8月, 2018 1 次提交