From: Kamal Dasu <kdasu.kdev@gmail.com>
To: keescook@chromium.org, linux-kernel@vger.kernel.org,
gmpy.liaowx@gmail.com, linux-mmc@vger.kernel.org
Cc: f.fainelli@gmail.com, tony.luck@intel.com, anton@enomsg.org,
Kamal Dasu <kdasu.kdev@gmail.com>
Subject: [RFC 0/1] mmc: Add mmc pstore backend support
Date: Fri, 16 Dec 2022 16:54:09 -0500 [thread overview]
Message-ID: <20221216215410.26960-1-kdasu.kdev@gmail.com> (raw)
Have been trying to provide mmc backend support for fs/pstore feature
to be able to capture panic and dmesg logs to a emmc partition. The code is
based on mtdpstore and used kernel mmctest also as reference to be able to
send mmc rw requests. This code is work in progress and does not succssfully
write to the mmc partition as expected when a magic sysrq panic is induced.
Needed help from original authors and mmc core and host driver experts to
comment on missing peices. To that end I am sending an RFC patch. I have
confirmed by enabling dynamic debug that mmcpstore read and panic_write
routines do get called by the fs/pstore/zone driver, however I do not see
expected results mounted /sys/fs/pstore after a reboot.
Kamal Dasu (1):
mmc: Add mmc pstore backend support
drivers/mmc/core/Kconfig | 13 +
drivers/mmc/core/Makefile | 1 +
drivers/mmc/core/block.c | 61 ++--
drivers/mmc/core/block.h | 9 +
drivers/mmc/core/core.c | 28 +-
drivers/mmc/core/mmcpstore.c | 594 +++++++++++++++++++++++++++++++++++
drivers/mmc/host/sdhci.c | 166 +++++-----
include/linux/mmc/host.h | 3 +
8 files changed, 746 insertions(+), 129 deletions(-)
create mode 100644 drivers/mmc/core/mmcpstore.c
--
2.17.1
next reply other threads:[~2022-12-16 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 21:54 Kamal Dasu [this message]
2022-12-16 21:54 ` [RFC 1/1] mmc: Add mmc pstore backend support Kamal Dasu
2022-12-17 9:45 ` Christian Löhle
2022-12-17 14:24 ` Christian Löhle
2022-12-22 19:00 ` Kamal Dasu
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=20221216215410.26960-1-kdasu.kdev@gmail.com \
--to=kdasu.kdev@gmail.com \
--cc=anton@enomsg.org \
--cc=f.fainelli@gmail.com \
--cc=gmpy.liaowx@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@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