public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: On "sh: Consolidate SH-Mobile CPU code in arch/sh/kernel/cpu/shmobile/."
Date: Thu, 19 Mar 2009 05:39:16 +0000	[thread overview]
Message-ID: <aec7e5c30903182239t63db89c2k15786bc83e4dfca@mail.gmail.com> (raw)
In-Reply-To: <49BF4B7C.2090607@st.com>

Hi Francesco!

On Wed, Mar 18, 2009 at 11:17 PM, Francesco VIRLINZI
<francesco.virlinzi@st.com> wrote:
> Hi Magnus
>>>
>>> For this reason in the interpreter there is no real instruction 'data'
>>> oriented...
>>> Each interpreter instruction works with the i-th element of an k-th
>>> ioresources.
>>>
>>
>> So you may pass the base address of some hardware block as a resource,
>> and then use offset from the base address to get to registers inside
>> the hardware block. Or did I misunderstand?
>>
>
> No you didn't. You are right the interpreter can manage registers inside the
> hardware block.

Good. Then we're on the same page!

>> I'd go with fixed sized operations where one operation is maximum one
>> cache line. And the first part of each operation has an instruction
>> that just does a jump to the beginning of the next operation (next or
>> same cache line). This jumping will go on until a magic end operation
>> is reached. That's how I would preload the operations.
>>
> Ok.

Do you think the above would work in your case?

>> So basically I'd like to get rid of the your resource + offset
>> abstraction and go with regular addresses. What do you think?
>>
>
> The main reason of 'resource + offset' was due on a different PMB usage
> model in our kernel.
> But more probably with your "relocator - linker" at runtime I should be able
> to close every issue.
>
>
> Do you have already some stuff/prototype?

No, no code exists at this point. I hope to find some time to hack up
a prototype next week. We probably need a couple of iterations before
we both are happy so I suspect the interpreter stuff would be 2.6.31
material. Is that ok, or do you have any special requirements from
your side?

I also need to focus on fixing up the clock framework and cpuidle. And
cpufreq of course. Many things. =)

Cheers,

/ magnus

  parent reply	other threads:[~2009-03-19  5:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  7:04 On "sh: Consolidate SH-Mobile CPU code in arch/sh/kernel/cpu/shmobile/." Francesco VIRLINZI
2009-03-17  7:15 ` Paul Mundt
2009-03-17 10:35 ` Francesco VIRLINZI
2009-03-17 11:31 ` Magnus Damm
2009-03-17 14:43 ` Francesco VIRLINZI
2009-03-18  9:53 ` Magnus Damm
2009-03-18 14:17 ` Francesco VIRLINZI
2009-03-19  5:39 ` Magnus Damm [this message]
2009-03-19  7:17 ` Francesco VIRLINZI
2009-03-23 10:29 ` Magnus Damm

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=aec7e5c30903182239t63db89c2k15786bc83e4dfca@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox