Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755862AbbEUX3d (ORCPT ); Thu, 21 May 2015 19:29:33 -0400 Received: from TYO202.gate.nec.co.jp ([210.143.35.52]:54861 "EHLO tyo202.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754067AbbEUX3c convert rfc822-to-8bit (ORCPT ); Thu, 21 May 2015 19:29:32 -0400 From: Naoya Horiguchi To: Xie XiuQi , "akpm@linux-foundation.org" CC: "rostedt@goodmis.org" , "gong.chen@linux.intel.com" , "mingo@redhat.com" , "bp@suse.de" , "tony.luck@intel.com" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "jingle.chen@huawei.com" , "sfr@canb.auug.org.au" , "rdunlap@infradead.org" , "jim.epost@gmail.com" Subject: Re: [PATCH v6 0/5] tracing: add trace event for memory-failure Thread-Topic: [PATCH v6 0/5] tracing: add trace event for memory-failure Thread-Index: AQHQk3ipXpGQ2jandUWG0Dn2pH8KT52GfdWA Date: Thu, 21 May 2015 23:28:22 +0000 Message-ID: <20150521232821.GA5502@hori1.linux.bs1.fc.nec.co.jp> References: <1432179685-11369-1-git-send-email-xiexiuqi@huawei.com> In-Reply-To: <1432179685-11369-1-git-send-email-xiexiuqi@huawei.com> Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.128.101.25] Content-Type: text/plain; charset="iso-2022-jp" Content-ID: Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2531 Lines: 68 On Thu, May 21, 2015 at 11:41:20AM +0800, Xie XiuQi wrote: > RAS user space tools like rasdaemon which base on trace event, could > receive mce error event, but no memory recovery result event. So, I > want to add this event to make this scenario complete. > > This patchset add a event at ras group for memory-failure. > > The output like below: > # tracer: nop > # > # entries-in-buffer/entries-written: 2/2 #P:24 > # > # _-----=> irqs-off > # / _----=> need-resched > # | / _---=> hardirq/softirq > # || / _--=> preempt-depth > # ||| / delay > # TASK-PID CPU# |||| TIMESTAMP FUNCTION > # | | | |||| | | > mce-inject-13150 [001] .... 277.019359: memory_failure_event: pfn 0x19869: recovery action for free buddy page: Delayed > > -- > v5->v6: > - fix a build error > - move ras_event.h under include/trace/events > - rebase on top of latest mainline > > v4->v5: > - fix a typo > - rebase on top of latest mainline > > v3->v4: > - rebase on top of latest linux-next > - update comments as Naoya's suggestion > - add #ifdef CONFIG_MEMORY_FAILURE for this trace event > - change type of action_result's param 3 to enum > > v2->v3: > - rebase on top of linux-next > - based on Steven Rostedt's "tracing: Add TRACE_DEFINE_ENUM() macro > to map enums to their values" patch set v1. > > v1->v2: > - Comment update > - Just passing 'result' instead of 'action_name[result]', > suggested by Steve. And hard coded there because trace-cmd > and perf do not have a way to process enums. > > Naoya Horiguchi (1): > trace, ras: move ras_event.h under include/trace/events I withdraw this patch because my assumption was wrong. > Xie XiuQi (4): > memory-failure: export page_type and action result > memory-failure: change type of action_result's param 3 to enum > tracing: add trace event for memory-failure > tracing: fix build error in mm/memory-failure.c This patchset depends on TRACE_DEFINE_ENUM patches, so base kernel version need to be v4.1-rc1 or later. So please do the rebasing before merging this series. Thanks, Naoya Horiguchi-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/