All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	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>,
	linux-efi@vger.kernel.org, Tony Luck <tony.luck@gmail.com>
Subject: Re: Progress on system crash traces with LTTng using DAX and pmem
Date: Sat, 13 Dec 2014 11:48:27 +0000	[thread overview]
Message-ID: <20141213114827.GA7761@console-pimps.org> (raw)
In-Reply-To: <864133911.4806.1414681896478.JavaMail.zimbra@efficios.com>

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, 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@console-pimps.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	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>,
	linux-efi@vger.kernel.org, Tony Luck <tony.luck@gmail.com>
Subject: Re: Progress on system crash traces with LTTng using DAX and pmem
Date: Sat, 13 Dec 2014 11:48:27 +0000	[thread overview]
Message-ID: <20141213114827.GA7761@console-pimps.org> (raw)
In-Reply-To: <864133911.4806.1414681896478.JavaMail.zimbra@efficios.com>

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

  reply	other threads:[~2014-12-13 11:48 UTC|newest]

Thread overview: 14+ 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-25 12:51   ` Mathieu Desnoyers
2014-10-27 18:48   ` Matthew Wilcox
2014-10-27 18:48     ` Matthew Wilcox
2014-10-30 15:01     ` Mathieu Desnoyers
2014-10-30 15:01       ` Mathieu Desnoyers
2015-01-25 14:55     ` Mathieu Desnoyers
2015-01-25 14:55       ` Mathieu Desnoyers
2014-10-28 10:54   ` Kirill A. Shutemov
2014-10-28 10:54     ` Kirill A. Shutemov
2014-10-30 15:11     ` Mathieu Desnoyers
2014-10-30 15:11       ` Mathieu Desnoyers
2014-12-13 11:48       ` Matt Fleming [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=20141213114827.GA7761@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=andi@firstfloor.org \
    --cc=kirill@shutemov.name \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=tony.luck@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.