From: Massimiliano Galanti <massiblue@libero.it>
To: Brian Gordon <legerde@gmail.com>, Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Aerospace and linux
Date: Thu, 10 Jun 2010 21:23:46 +0200 [thread overview]
Message-ID: <4C113BC2.6070000@libero.it> (raw)
In-Reply-To: <AANLkTinIAKHVYKiILxQZXTr30K_Cr5EZQwRzNpYlLULw@mail.gmail.com>
> What about .ro and .text sections of an executable? I would think
> kernel support for that would be required. If its application data,
> then all sorts of things are possible like you described. Ive also
> seen critical ram variables be stored in triplicate and then
> compared/voted just to ensure no silent SEU corruption.
Maybe slightly off topic but... if flash is safer than ram, what about
using XIP (where possible, e.g. on NORs)? That would not put .data
sections into ram, at least.
--
Massimiliano
next prev parent reply other threads:[~2010-06-10 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:29 Aerospace and linux Brian Gordon
2010-06-10 18:23 ` Andi Kleen
2010-06-10 18:38 ` Brian Gordon
2010-06-10 18:46 ` Chris Friesen
2010-06-10 19:14 ` Brian Gordon
2010-06-10 18:48 ` Andi Kleen
2010-06-13 8:51 ` Borislav Petkov
2010-06-10 18:27 ` Chris Friesen
2010-06-10 18:42 ` Brian Gordon
2010-06-10 19:23 ` Massimiliano Galanti [this message]
2010-06-10 19:37 ` Brian Gordon
2010-06-10 19:42 ` Brian Gordon
2010-06-10 19:52 ` Massimiliano Galanti
2010-06-10 20:12 ` Brian Gordon
2010-06-10 19:59 ` Massimiliano Galanti
2010-06-11 14:37 ` Henrique de Moraes Holschuh
-- strict thread matches above, loose matches on Subject: below --
2010-06-13 15:26 Denys Fedorysychenko
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=4C113BC2.6070000@libero.it \
--to=massiblue@libero.it \
--cc=cfriesen@nortel.com \
--cc=legerde@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.