linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vimal.newwork@gmail.com (Vimal Singh)
To: linux-arm-kernel@lists.infradead.org
Subject: Self modifying code in ARM 11 architectures
Date: Wed, 25 May 2011 13:18:37 +0530	[thread overview]
Message-ID: <BANLkTinrj-dkJShzTQuhYSOWkK4QSEnQgQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimyju7eEgtCpb_U6s8LNHk-_FGK4Q@mail.gmail.com>

CC'ing correct ARM mailing list.

On Tue, May 24, 2011 at 3:48 PM, Ashok Babu <ashok3d@gmail.com> wrote:
> Hi All,
>
> I am no success in booting up the ARM1176 processor with the
> linux-2.6.32 kernel.
> While googling about the ARM?Harvard?architecture, I came to know that
> we have to flush/invalidate the D-Cache and I-Cache
> when using the self modifying codes.
>
> So here my questions/doubts :
> 1) Is'nt it the kernel itself is self modifying code with lots of
> function pointers ?
> ? ? If yes, how is synchronization b/w d-cache and i-cache handled in
> the kernel ?
> 2) Can this be the reason for the kernel not booting for me ?
> ? ? Because If i disable the I-Cache in the config, then the kernel
> boots up without any issues.
> Any pointers on this will be of great help.
>
> Thanks & Best Regards
> Ashok
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>



-- 
Regards,
Vimal Singh

       reply	other threads:[~2011-05-25  7:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTi=mVsYiubqtJO2BmWvExMvUFRg6dg@mail.gmail.com>
     [not found] ` <BANLkTimyju7eEgtCpb_U6s8LNHk-_FGK4Q@mail.gmail.com>
2011-05-25  7:48   ` Vimal Singh [this message]
2011-05-25 11:45     ` Self modifying code in ARM 11 architectures Uwe Kleine-König

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=BANLkTinrj-dkJShzTQuhYSOWkK4QSEnQgQ@mail.gmail.com \
    --to=vimal.newwork@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).