From: "Stephen Williams" <612dlag102@sneakemail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [RFC] "indirect" DCR access (40x, BookE)
Date: Thu, 11 Mar 2004 20:44:09 -0800 [thread overview]
Message-ID: <24019-11838@sneakemail.com> (raw)
In-Reply-To: <20040312030502.GA25644@gate.ebshome.net>
Eugene Surovegin ebs-at-ebshome.net |PPC Linux Embedded| wrote:
> On Thu, Mar 11, 2004 at 09:46:59PM -0500, Dan Malek wrote:
>
>>>Comments, suggestions are welcome.
>>
>>I think you should just write it as self modifying code :-)
>>Write the instruction with the DCR number and just execute it.
>
>
> And deal with locking and icache/dcache coherency ?
>
> No, thanks :)
Actually, I recall that there is a code fixup mechanism that
is invoked early in kernel init that does exactly that: it
manages some machine specific differences by editing the code
in place in a safe way. My memory is not good enough to point
to the right place in the code, though, or to explain how it
works.
--
Steve Williams "The woods are lovely, dark and deep.
steve at XXXXXXXXXX But I have promises to keep,
http://www.XXXXXXXXXX and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-12 4:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 1:48 [RFC] "indirect" DCR access (40x, BookE) Eugene Surovegin
2004-03-12 2:46 ` Dan Malek
2004-03-12 3:05 ` Eugene Surovegin
2004-03-12 4:44 ` Stephen Williams [this message]
2004-03-12 4:54 ` Eugene Surovegin
2004-03-12 14:25 ` Kumar Gala
2004-03-12 14:53 ` Chuck Meade
2004-03-12 16:20 ` Eugene Surovegin
2004-03-12 18:01 ` Dan Malek
2004-03-19 4:00 ` Benjamin Herrenschmidt
2004-03-23 2:47 ` Eugene Surovegin
2004-04-01 5:36 ` Kumar Gala
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=24019-11838@sneakemail.com \
--to=612dlag102@sneakemail.com \
--cc=linuxppc-embedded@lists.linuxppc.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.