From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kirill A. Shutemov" Subject: Re: Progress on system crash traces with LTTng using DAX and pmem Date: Tue, 28 Oct 2014 12:54:58 +0200 Message-ID: <20141028105458.GA9768@node.dhcp.inet.fi> References: <1254279794.1957.1414240389301.JavaMail.zimbra@efficios.com> <465653369.1985.1414241485934.JavaMail.zimbra@efficios.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matthew Wilcox , Ross Zwisler , lttng-dev , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org To: Mathieu Desnoyers Return-path: Content-Disposition: inline In-Reply-To: <465653369.1985.1414241485934.JavaMail.zimbra@efficios.com> Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Oct 25, 2014 at 12:51:25PM +0000, Mathieu Desnoyers wrote: > FYI, the main reason why my customer wants to go with a > "trace into memory that survives soft reboot" approach > rather than to use things like kexec/kdump is that they > care about the amount of time it takes to reboot their > machines. They want a solution where they can extract the > detailed crash data after reboot, after the machine is > back online, rather than requiring a few minutes of offline > time to extract the crash details. IIRC, on x86 there's no guarantee that your memory content will be preserved over reboot. BIOS is free to mess with it. -- Kirill A. Shutemov -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org