From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Matthew Wilcox <willy@linux.intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
lttng-dev <lttng-dev@lists.lttng.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: Progress on system crash traces with LTTng using DAX and pmem
Date: Thu, 30 Oct 2014 15:11:36 +0000 (UTC) [thread overview]
Message-ID: <864133911.4806.1414681896478.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20141028105458.GA9768@node.dhcp.inet.fi>
----- Original Message -----
> From: "Kirill A. Shutemov" <kirill@shutemov.name>
> To: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
> Cc: "Matthew Wilcox" <willy@linux.intel.com>, "Ross Zwisler" <ross.zwisler@linux.intel.com>, "lttng-dev"
> <lttng-dev@lists.lttng.org>, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
> Sent: Tuesday, October 28, 2014 6:54:58 AM
> Subject: Re: Progress on system crash traces with LTTng using DAX and pmem
>
> 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.
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 ?
Thoughts ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2014-10-30 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1254279794.1957.1414240389301.JavaMail.zimbra@efficios.com>
2014-10-25 12:51 ` Progress on system crash traces with LTTng using DAX and pmem Mathieu Desnoyers
2014-10-27 18:48 ` Matthew Wilcox
2014-10-30 15:01 ` Mathieu Desnoyers
2015-01-25 14:55 ` Mathieu Desnoyers
2014-10-28 10:54 ` Kirill A. Shutemov
2014-10-30 15:11 ` Mathieu Desnoyers [this message]
2014-12-13 11:48 ` Matt Fleming
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=864133911.4806.1414681896478.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=andi@firstfloor.org \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lttng-dev@lists.lttng.org \
--cc=ross.zwisler@linux.intel.com \
--cc=willy@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).