public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: x86@kernel.org, Borislav Petkov <bp@alien8.de>,
	Chen Gong <gong.chen@linux.jf.intel.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] extlog trace event - queue for 3.17
Date: Mon, 30 Jun 2014 09:54:00 -0700	[thread overview]
Message-ID: <53b196284053a30cc@agluck-desk.sc.intel.com> (raw)

The following changes since commit 4d4c9cc839a308be3289a361ccba4447ee140552:

  tracing: Add __field_struct macro for TRACE_EVENT() (2014-06-21 00:18:42 -0400)

[Note this base commit was pulled by Linus between 3.16-rc2 and -rc3]

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/please-pull-extlog-trace

for you to fetch changes up to 7c76bb5f7a3d052339b873374333dd0dcc35ce28:

  RAS, extlog: Adjust init flow (2014-06-25 13:27:26 -0700)

----------------------------------------------------------------
Report extended error information ("extlog") using
a trace/event.  Provide a mechanism for a smart
daemon collecting this information to tell the kernel
to skip logging corrected errors to the console.

----------------------------------------------------------------
Chen, Gong (7):
      trace, RAS: Add basic RAS trace event
      trace, AER: Move trace into unified interface
      CPER: Adjust code flow of some functions
      RAS, debugfs: Add debugfs interface for RAS subsystem
      trace, RAS: Add eMCA trace event interface
      trace, eMCA: Add a knob to adjust where to save event log
      RAS, extlog: Adjust init flow

 drivers/Kconfig                        |   2 +
 drivers/Makefile                       |   1 +
 drivers/acpi/Kconfig                   |   4 +-
 drivers/acpi/acpi_extlog.c             |  46 ++++++--
 drivers/edac/Kconfig                   |   1 +
 drivers/edac/edac_mc.c                 |   3 -
 drivers/firmware/efi/cper.c            | 192 +++++++++++++++++++++++----------
 drivers/pci/pcie/aer/Kconfig           |   1 +
 drivers/pci/pcie/aer/aerdrv_errprint.c |   4 +-
 drivers/ras/Kconfig                    |   2 +
 drivers/ras/Makefile                   |   1 +
 drivers/ras/debugfs.c                  |  56 ++++++++++
 drivers/ras/ras.c                      |  29 +++++
 include/linux/cper.h                   |  32 ++++++
 include/linux/ras.h                    |  14 +++
 include/ras/ras_event.h                | 128 ++++++++++++++++++++++
 include/trace/events/ras.h             |  77 -------------
 17 files changed, 443 insertions(+), 150 deletions(-)
 create mode 100644 drivers/ras/Kconfig
 create mode 100644 drivers/ras/Makefile
 create mode 100644 drivers/ras/debugfs.c
 create mode 100644 drivers/ras/ras.c
 create mode 100644 include/linux/ras.h
 delete mode 100644 include/trace/events/ras.h

                 reply	other threads:[~2014-06-30 16:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53b196284053a30cc@agluck-desk.sc.intel.com \
    --to=tony.luck@intel.com \
    --cc=bp@alien8.de \
    --cc=gong.chen@linux.jf.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=x86@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