Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756046Ab1EXDID (ORCPT ); Mon, 23 May 2011 23:08:03 -0400 Received: from mga01.intel.com ([192.55.52.88]:28877 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753987Ab1EXDIA (ORCPT ); Mon, 23 May 2011 23:08:00 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,259,1304319600"; d="scan'208";a="7524888" Message-ID: <4DDB210D.6060202@intel.com> Date: Tue, 24 May 2011 11:07:57 +0800 From: Huang Ying User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110402 Iceowl/1.0b2 Icedove/3.1.9 MIME-Version: 1.0 To: Ingo Molnar CC: huang ying , Len Brown , "linux-kernel@vger.kernel.org" , Andi Kleen , "Luck, Tony" , "linux-acpi@vger.kernel.org" , Andi Kleen , "Wu, Fengguang" , Andrew Morton , Linus Torvalds , Peter Zijlstra , Borislav Petkov Subject: Re: [PATCH 5/9] HWPoison: add memory_failure_queue() References: <20110517092620.GI22093@elte.hu> <4DD31C78.6000209@intel.com> <20110520115614.GH14745@elte.hu> <20110522100021.GA28177@elte.hu> <20110522132515.GA13078@elte.hu> <4DD9C8B9.5070004@intel.com> <20110523110151.GD24674@elte.hu> <4DDB1396.7050205@intel.com> <20110524024848.GA25230@elte.hu> In-Reply-To: <20110524024848.GA25230@elte.hu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2141 Lines: 46 On 05/24/2011 10:48 AM, Ingo Molnar wrote: > > * Huang Ying wrote: > >>>> - How to deal with ring-buffer overflow? For example, there is full of >>>> corrected memory error in ring-buffer, and now a recoverable memory error >>>> occurs but it can not be put into perf ring buffer because of ring-buffer >>>> overflow, how to deal with the recoverable memory error? >>> >>> The solution is to make it large enough. With *every* queueing solution there >>> will be some sort of queue size limit. >> >> Another solution could be: >> >> Create two ring-buffer. One is for logging and will be read by RAS >> daemon; the other is for recovering, the event record will be removed >> from the ring-buffer after all 'active filters' have been run on it. >> Even RAS daemon being restarted or hang, recoverable error can be taken >> cared of. > > Well, filters will always be executed since they execute when the event is > inserted - not when it's extracted. For filters executed in NMI context, they can be executed when the event is inserted, no need for buffering. But for filters executed in deferred IRQ context, they need to be executed when event's extracted. > So if you worry about losing *filter* executions (and dependent policy action) > - there should be no loss there, ever. > > But yes, the scheme you outline would work as well: a counting-only event with > a filter specified - this will do no buffering at all. > > So ... to get the ball rolling in this area one of you guys active in RAS > should really try a first approximation for the active filter approach: add a > test-TRACE_EVENT() for the errors you are interested in and define a convenient > way to register policy action with post-filter events. This should work even > without having the 'active' portion defined at the ABI and filter-string level. Best Regards, Huang Ying -- 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/