public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takao Indoh <indou.takao@jp.fujitsu.com>
To: <alexander.shishkin@linux.intel.com>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <hpa@zytor.com>, <a.p.zijlstra@chello.nl>,
	<acme@kernel.org>, <vgoyal@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH RFC 0/3] x86: Intel Processor Trace Logger
Date: Wed, 29 Jul 2015 14:51:52 +0900	[thread overview]
Message-ID: <55B869F8.5030404@jp.fujitsu.com> (raw)
In-Reply-To: <878u9zbjra.fsf@ashishki-desk.ger.corp.intel.com>

On 2015/07/29 14:44, Alexander Shishkin wrote:
> Takao Indoh <indou.takao@jp.fujitsu.com> writes:
> 
>> Hi all,
>>
>> This patch creates log buffer for Intel PT and enable logging at boot
>> time. When kernel panic occurs, we can get this log buffer from
>> crashdump file by kdump, and reconstruct the flow that led to the panic.
> 
> Good to see this work going forward!
> 
>> Takao Indoh (3):
>>    x86: Add Intel PT common files
>>    x86: Add Intel PT logger
>>    x86: Stop Intel PT and save its registers when panic occurs
>>
>>   arch/x86/Kconfig                          |   16 ++
>>   arch/x86/include/asm/intel_pt.h           |   84 +++++++++
>>   arch/x86/kernel/cpu/Makefile              |    3 +
>>   arch/x86/kernel/cpu/intel_pt.h            |  131 -------------
>>   arch/x86/kernel/cpu/intel_pt_cap.c        |   69 +++++++
>>   arch/x86/kernel/cpu/intel_pt_log.c        |  288 +++++++++++++++++++++++++++++
>>   arch/x86/kernel/cpu/intel_pt_perf.h       |   78 ++++++++
>>   arch/x86/kernel/cpu/perf_event_intel_pt.c |   54 +-----
>>   arch/x86/kernel/crash.c                   |    9 +
>>   9 files changed, 556 insertions(+), 176 deletions(-)
>>   create mode 100644 arch/x86/include/asm/intel_pt.h
>>   delete mode 100644 arch/x86/kernel/cpu/intel_pt.h
>>   create mode 100644 arch/x86/kernel/cpu/intel_pt_cap.c
>>   create mode 100644 arch/x86/kernel/cpu/intel_pt_log.c
>>   create mode 100644 arch/x86/kernel/cpu/intel_pt_perf.h
> 
> One note here: you want to use -M with git-format-patch so that renames
> are handled better.

Thank you, I didn't know this option. I'll do next time.

Thanks,
Takao Indoh


> 
> Regards,
> --
> Alex
> 



      reply	other threads:[~2015-07-29  5:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  4:51 [PATCH RFC 0/3] x86: Intel Processor Trace Logger Takao Indoh
2015-07-29  4:51 ` [PATCH RFC 1/3] x86: Add Intel PT common files Takao Indoh
2015-08-02 10:02   ` Thomas Gleixner
2015-08-03  3:14     ` Takao Indoh
2015-07-29  4:51 ` [PATCH RFC 2/3] x86: Add Intel PT logger Takao Indoh
2015-07-29  6:08   ` Alexander Shishkin
2015-07-29  8:13     ` Takao Indoh
2015-07-29  9:09       ` Alexander Shishkin
2015-07-30  1:49         ` Takao Indoh
2015-07-30  5:32           ` Alexander Shishkin
2015-08-26  8:10     ` Takao Indoh
2015-07-29  4:51 ` [PATCH RFC 3/3] x86: Stop Intel PT and save its registers when panic occurs Takao Indoh
2015-07-29  5:44 ` [PATCH RFC 0/3] x86: Intel Processor Trace Logger Alexander Shishkin
2015-07-29  5:51   ` Takao Indoh [this message]

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=55B869F8.5030404@jp.fujitsu.com \
    --to=indou.takao@jp.fujitsu.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@redhat.com \
    --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