linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: "Luck, Tony" <tony.luck@intel.com>, lkml <linux-kernel@vger.kernel.org>
Cc: "keescook@chromium.org" <keescook@chromium.org>,
	Anton Vorontsov <anton@enomsg.org>,
	"ccross@android.com" <ccross@android.com>
Subject: Re: Pstore : Query on using ramoops driver for DDR
Date: Wed, 10 Feb 2021 21:03:20 +0530	[thread overview]
Message-ID: <9a653cf1-ab22-15c1-d021-a7cfe2b78276@codeaurora.org> (raw)
In-Reply-To: <e28daeb8a1d74d60a3acb5c582f92123@intel.com>


On 2/10/2021 2:32 AM, Luck, Tony wrote:
>> Can we use existing backend pstore ram driver (fs/pstore/ram.c) for DDR
>> instead of SRAM ?
> The expectation for pstore is that the system will go through a reset when it
> crashes. Most systems do not preserve DDR contents across reset.
>
> to support DDR, If we have a mechanism to copy stored data from DDR to
> external device after the crash.
>> Was the current driver written only to support persistant RAM like SRAM
>> or it can accept further change
> Linux is in a constant state of change :-)
>
> See above about DDR contents.   But if you have a platform that does preserve
> DDR contents until your "mechanism" can copy the pstore buffer, then post
> a patch.

Thanks for the reply

I have posted the patch.

https://lore.kernel.org/patchwork/patch/1378949/

-Mukesh


>

> -Tony

      reply	other threads:[~2021-02-10 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 20:46 Pstore : Query on using ramoops driver for DDR Mukesh Ojha
2021-02-09 21:02 ` Luck, Tony
2021-02-10 15:33   ` Mukesh Ojha [this message]

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=9a653cf1-ab22-15c1-d021-a7cfe2b78276@codeaurora.org \
    --to=mojha@codeaurora.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@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).