mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Tom Zanussi <zanussi@kernel.org>
Subject: [GIT PULL] tracing/bootconfig: Fixes and changes to bootconfig before it goes live in a release
Date: Tue, 25 Feb 2020 19:19:27 -0500	[thread overview]
Message-ID: <20200225191927.3cbaa0db@gandalf.local.home> (raw)


Linus,

Tracing updates:

 Change in API of bootconfig (before it comes live in a release)
  - Have a magic value "BOOTCONFIG" in initrd to know a bootconfig exists
  - Set CONFIG_BOOT_CONFIG to 'n' by default
  - Show error if "bootconfig" on cmdline but not compiled in
  - Prevent redefining the same value
  - Have a way to append values
  - Added a SELECT BLK_DEV_INITRD to fix a build failure

 Synthetic event fixes:
  - Switch to raw_smp_processor_id() for recording CPU value in preempt
    section. (No care for what the value actually is)
  - Fix samples always recording u64 values
  - Fix endianess
  - Check number of values matches number of fields
  - Fix a printing bug

 Fix of trace_printk() breaking postponed start up tests

 Make a function static that is only used in a single file.


Please pull the latest trace-v5.6-rc2 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v5.6-rc2

Tag SHA1: b50d255b6c6f55384c40bbac65fd5d5d4529a8ba
Head SHA1: 2910b5aa6f545c044173a5cab3dbb7f43e23916d


Masami Hiramatsu (9):
      tracing: Clear trace_state when starting trace
      bootconfig: Set CONFIG_BOOT_CONFIG=n by default
      bootconfig: Add bootconfig magic word for indicating bootconfig explicitly
      tools/bootconfig: Remove unneeded error message silencer
      bootconfig: Reject subkey and value on same parent key
      bootconfig: Print array as multiple commands for legacy command line
      bootconfig: Prohibit re-defining value on same key
      bootconfig: Add append value operator support
      bootconfig: Fix CONFIG_BOOTTIME_TRACING dependency issue

Qiujun Huang (1):
      bootconfig: Mark boot_config_checksum() static

Steven Rostedt (VMware) (2):
      tracing: Have synthetic event test use raw_smp_processor_id()
      tracing: Disable trace_printk() on post poned tests

Tom Zanussi (4):
      tracing: Make sure synth_event_trace() example always uses u64
      tracing: Make synth_event trace functions endian-correct
      tracing: Check that number of vals matches number of synth event fields
      tracing: Fix number printing bug in print_synth_event()

----
 Documentation/admin-guide/bootconfig.rst     |  34 +++++++-
 include/linux/bootconfig.h                   |   3 +
 init/Kconfig                                 |   5 +-
 init/main.c                                  |  38 +++++----
 kernel/trace/Kconfig                         |   4 +-
 kernel/trace/synth_event_gen_test.c          |  44 +++++------
 kernel/trace/trace.c                         |   2 +
 kernel/trace/trace_events_hist.c             | 112 ++++++++++++++++++++++++---
 lib/bootconfig.c                             |  36 ++++++---
 tools/bootconfig/include/linux/printk.h      |   5 +-
 tools/bootconfig/main.c                      |  51 +++++++-----
 tools/bootconfig/samples/bad-mixed-kv1.bconf |   3 +
 tools/bootconfig/samples/bad-mixed-kv2.bconf |   3 +
 tools/bootconfig/samples/bad-samekey.bconf   |   6 ++
 tools/bootconfig/test-bootconfig.sh          |  18 ++++-
 15 files changed, 272 insertions(+), 92 deletions(-)
 create mode 100644 tools/bootconfig/samples/bad-mixed-kv1.bconf
 create mode 100644 tools/bootconfig/samples/bad-mixed-kv2.bconf
 create mode 100644 tools/bootconfig/samples/bad-samekey.bconf
---------------------------

             reply	other threads:[~2020-02-26  0:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26  0:19 Steven Rostedt [this message]
2020-02-26 18:50 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200225191927.3cbaa0db@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zanussi@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®