From: Fernando Guzman Lugo <fernando.lugo@ti.com>
To: <ohad@wizery.com>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>
Subject: [PATCHv2 0/3] remoteproc: introduce rproc recovery
Date: Thu, 30 Aug 2012 13:26:11 -0500 [thread overview]
Message-ID: <1346351174-28441-1-git-send-email-fernando.lugo@ti.com> (raw)
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the remoteproc is reset and it will
start from the beginning. When a crash happen all the virtio devices are
destroyed. Therefore, both rpmsg drivers and devices are gracefully
removed which also cause rproc users become 0 and the remoteproc is turned
off. After the virtio devices are destroyed the crash handler function
will read the virtio information from the firmware in order to recreate
the virtio devices that will boot the remoteproc and everything will be
functional again.
-Version 2
* Wait untill there is no more rproc users before realoding the FW again
in order to make sure the recovery will work fine. As suggested by
Sjur BRENDELAND
Fernando Guzman Lugo (3):
remoteproc: add rproc_report_crash function to notify rproc crashes
remoteproc: recover a remoteproc when it has crashed
remoteproc: create debugfs entry to disable/enable recovery
dynamically
Documentation/remoteproc.txt | 7 ++
drivers/remoteproc/remoteproc_core.c | 116 ++++++++++++++++++++++++++++--
drivers/remoteproc/remoteproc_debugfs.c | 83 +++++++++++++++++++++
drivers/remoteproc/remoteproc_internal.h | 1 +
include/linux/remoteproc.h | 22 ++++++
5 files changed, 222 insertions(+), 7 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Fernando Guzman Lugo <fernando.lugo@ti.com>
To: ohad@wizery.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Fernando Guzman Lugo <fernando.lugo@ti.com>
Subject: [PATCHv2 0/3] remoteproc: introduce rproc recovery
Date: Thu, 30 Aug 2012 13:26:11 -0500 [thread overview]
Message-ID: <1346351174-28441-1-git-send-email-fernando.lugo@ti.com> (raw)
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the remoteproc is reset and it will
start from the beginning. When a crash happen all the virtio devices are
destroyed. Therefore, both rpmsg drivers and devices are gracefully
removed which also cause rproc users become 0 and the remoteproc is turned
off. After the virtio devices are destroyed the crash handler function
will read the virtio information from the firmware in order to recreate
the virtio devices that will boot the remoteproc and everything will be
functional again.
-Version 2
* Wait untill there is no more rproc users before realoding the FW again
in order to make sure the recovery will work fine. As suggested by
Sjur BRENDELAND
Fernando Guzman Lugo (3):
remoteproc: add rproc_report_crash function to notify rproc crashes
remoteproc: recover a remoteproc when it has crashed
remoteproc: create debugfs entry to disable/enable recovery
dynamically
Documentation/remoteproc.txt | 7 ++
drivers/remoteproc/remoteproc_core.c | 116 ++++++++++++++++++++++++++++--
drivers/remoteproc/remoteproc_debugfs.c | 83 +++++++++++++++++++++
drivers/remoteproc/remoteproc_internal.h | 1 +
include/linux/remoteproc.h | 22 ++++++
5 files changed, 222 insertions(+), 7 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: fernando.lugo@ti.com (Fernando Guzman Lugo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] remoteproc: introduce rproc recovery
Date: Thu, 30 Aug 2012 13:26:11 -0500 [thread overview]
Message-ID: <1346351174-28441-1-git-send-email-fernando.lugo@ti.com> (raw)
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the remoteproc is reset and it will
start from the beginning. When a crash happen all the virtio devices are
destroyed. Therefore, both rpmsg drivers and devices are gracefully
removed which also cause rproc users become 0 and the remoteproc is turned
off. After the virtio devices are destroyed the crash handler function
will read the virtio information from the firmware in order to recreate
the virtio devices that will boot the remoteproc and everything will be
functional again.
-Version 2
* Wait untill there is no more rproc users before realoding the FW again
in order to make sure the recovery will work fine. As suggested by
Sjur BRENDELAND
Fernando Guzman Lugo (3):
remoteproc: add rproc_report_crash function to notify rproc crashes
remoteproc: recover a remoteproc when it has crashed
remoteproc: create debugfs entry to disable/enable recovery
dynamically
Documentation/remoteproc.txt | 7 ++
drivers/remoteproc/remoteproc_core.c | 116 ++++++++++++++++++++++++++++--
drivers/remoteproc/remoteproc_debugfs.c | 83 +++++++++++++++++++++
drivers/remoteproc/remoteproc_internal.h | 1 +
include/linux/remoteproc.h | 22 ++++++
5 files changed, 222 insertions(+), 7 deletions(-)
next reply other threads:[~2012-08-30 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 18:26 Fernando Guzman Lugo [this message]
2012-08-30 18:26 ` [PATCHv2 0/3] remoteproc: introduce rproc recovery Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-08-30 18:26 ` [PATCHv2 1/3] remoteproc: add rproc_report_crash function to notify rproc crashes Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-08-30 18:26 ` [PATCHv2 2/3] remoteproc: recover a remoteproc when it has crashed Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-08-30 18:26 ` [PATCHv2 3/3] remoteproc: create debugfs entry to disable/enable recovery dynamically Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-08-30 18:26 ` Fernando Guzman Lugo
2012-09-18 9:59 ` [PATCHv2 0/3] remoteproc: introduce rproc recovery Ohad Ben-Cohen
2012-09-18 9:59 ` Ohad Ben-Cohen
2012-09-18 18:25 ` Fernando Lugo
2012-09-18 18:25 ` Fernando Lugo
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=1346351174-28441-1-git-send-email-fernando.lugo@ti.com \
--to=fernando.lugo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.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.