public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: cache-l2x0: add resume entry for l2 in secure mode
Date: Wed, 21 Sep 2011 08:51:37 +0100	[thread overview]
Message-ID: <20110921075137.GE17169@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAGsJ_4xcWkGYrRoR_uSwtW6Qt4TkSWp+yQemP36sdF8o_Q=bLw@mail.gmail.com>

On Wed, Sep 21, 2011 at 03:49:23PM +0800, Barry Song wrote:
> 2011/9/21 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> > On Wed, Sep 21, 2011 at 01:53:37PM +0800, Barry Song wrote:
> >> yes. imx6q actually needs to enable l2 earlier than cpu_resume(and mmu
> >> resume). so how about letting outer_resume support both phy and virt
> >> address restore?
> >
> > You can't call C functions in the kernel before the MMU is enabled.
> 
> well. a direct call will fall into virtual address. then we need to
> transfer it to a phy address before calling it.

No.  I say again, you can't call C functions in the kernel before the
MMU is enabled.

C functions have literal tables that contain absolute virtual addresses
of variables and such like.  Without the MMU enabled, those addresses
are meaningless and won't point at the right place.

  reply	other threads:[~2011-09-21  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  1:57 [PATCH] ARM: cache-l2x0: add resume entry for l2 in secure mode Barry Song
2011-09-21  5:52 ` Shawn Guo
2011-09-21  5:53   ` Barry Song
2011-09-21  6:58     ` Shawn Guo
2011-09-21  7:38     ` Russell King - ARM Linux
2011-09-21  7:49       ` Barry Song
2011-09-21  7:51         ` Russell King - ARM Linux [this message]
2011-09-21  7:53         ` Barry Song

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=20110921075137.GE17169@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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