From: arlie@worldash.org (Arlie Stephens)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [ARM_LINUX] ioremap() allowing to map system memory...
Date: Fri, 1 Mar 2013 09:56:02 -0800 [thread overview]
Message-ID: <20130301175602.GA27467@worldash.org> (raw)
In-Reply-To: <49572.1362158957@turing-police.cc.vt.edu>
On Mar 01 2013, Valdis.Kletnieks at vt.edu wrote:
> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.4-dev
>
> On Fri, 01 Mar 2013 16:48:12 +0530, sandeep kumar said:
>
> > Don't you think it should throw panic()while calling the ioremap() itself.
> > Because this sounds like a serious violation...
>
> As you noted, it does give you a warning.
>
> That's a kernel design philosophy - to reserve the panic() and BUG()
> calls for cases where it is *known* that proceeding further is
> unsafe or impossible. So the kernel does a panic() if it can't start
> /sbin/init at system boot-up - because without that, further progress
> is impossible. But once the system is up, we don't panic if PID 1 goes
> away - because it's possible that the user has an open window, and can su
> and at least do an orderly shutdown.
[snippage]
> So that's the design philosophy of why it gives you a warning rather than
> a panic.
Great explanation. Thank you.
I figured it would be something vaguely like this, but I'm very new to
the *linux* kernel, so I wasn't going to try to answer.
--
Arlie
(Arlie Stephens arlie at worldash.org)
prev parent reply other threads:[~2013-03-01 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 11:18 [ARM_LINUX] ioremap() allowing to map system memory sandeep kumar
2013-03-01 11:28 ` Prabhu nath
2013-03-01 12:27 ` sandeep kumar
2013-03-02 11:22 ` Prabhu nath
2013-03-02 17:18 ` sandeep kumar
2013-03-04 8:02 ` buyitian
2013-03-04 9:48 ` sandeep kumar
2013-03-01 17:29 ` Valdis.Kletnieks at vt.edu
2013-03-01 17:56 ` Arlie Stephens [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=20130301175602.GA27467@worldash.org \
--to=arlie@worldash.org \
--cc=kernelnewbies@lists.kernelnewbies.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 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).