Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030537AbaLMLsd (ORCPT ); Sat, 13 Dec 2014 06:48:33 -0500 Received: from mail-wi0-f179.google.com ([209.85.212.179]:50079 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030489AbaLMLsa (ORCPT ); Sat, 13 Dec 2014 06:48:30 -0500 Date: Sat, 13 Dec 2014 11:48:27 +0000 From: Matt Fleming To: Mathieu Desnoyers Cc: "Kirill A. Shutemov" , Matthew Wilcox , Ross Zwisler , lttng-dev , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andi Kleen , linux-efi@vger.kernel.org, Tony Luck Subject: Re: Progress on system crash traces with LTTng using DAX and pmem Message-ID: <20141213114827.GA7761@console-pimps.org> References: <1254279794.1957.1414240389301.JavaMail.zimbra@efficios.com> <465653369.1985.1414241485934.JavaMail.zimbra@efficios.com> <20141028105458.GA9768@node.dhcp.inet.fi> <864133911.4806.1414681896478.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <864133911.4806.1414681896478.JavaMail.zimbra@efficios.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Oct, at 03:11:36PM, Mathieu Desnoyers wrote: > > Hi Kirill, > > This is a good point, > > There are a few more aspects to consider here: > > - Other architectures appear to have different guarantees, for > instance ARM which, AFAIK, does not reset memory on soft > reboot (well at least for my customer's boards). So I guess > if x86 wants to be competitive, it would be good for them to > offer a similar feature, > > - Already having a subset of machines supporting this is useful, > e.g. storing trace buffers and recovering them after a crash, > > - Since we are in a world of dynamically upgradable BIOS, perhaps > if we can show that there is value in having a BIOS option to > specify a memory range that should not be reset on soft reboot, > BIOS vendors might be inclined to include an option for it, > > - Perhaps UEFI BIOS already have some way of specifying that a > memory range should not be reset on soft reboot ? We've achieved this in the past using UEFI capsules with the EFI_CAPSULE_PERSIST_ACROSS_RESET header flag. Unfortunately, runtime capsule support is pretty spotty, so it's not a general solution right now. -- Matt Fleming, Intel Open Source Technology Center -- 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/