Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-arch@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC PATCH 0/9] Thumb-2 ISA kernel port
Date: Wed, 06 Jun 2007 23:02:29 +0100	[thread overview]
Message-ID: <1181167349.27659.49.camel@localhost.localdomain> (raw)
In-Reply-To: <20070606182914.GB6303@uranus.ravnborg.org>

On Wed, 2007-06-06 at 20:29 +0200, Sam Ravnborg wrote:
> Can you please share with us the strong arguments why another (third)
> arm architecture are needed?

Well, it's not a strong argument but Thumb-2 is a different instruction
set. Even though there is a unified assembly language which tries to
reduce/eliminate the gap between ARM and Thumb, there are still
differences and, probably the most important, older toolchains don't
support it.

> Browsing through your patches there seems to be a common pattern:
> 1) Adding a bit more info to many assembler function
> 2) Small modifications to assembler function
> 3) Almost replaced assembler functions
> 4) Simpler Kconfig and Makefile
> 
> 
> 1) Could be solved in trivial ways using a few macros.
>    One example:
>    .type   printhex8, %function

Yes, this is needed so that the linker knows that the address of
printhex8 should have bit 1 set and also generate BL instead of BLX
instructions.

Adding this to the ARM code is harmless anyway (and I think we should
probably do it anyway). As Russell said, there is a macro already for
this.

> 2) For some parts it looked like:
>    "We can do this different so lets do it different"
>    I am rather ARM assembler ignorant so that may not hold true.
                 ^^^^^^^^^^^^^^^^^^^^^^
Indeed, it doesn't hold true :-). I tried to modify as little as
possible but see the Thumb-2 limitations in my original post for why it
isn't possible to use the existing code (not all variants of ldm/stm,
ldr/str, different model for exception return etc.).

> 3) Factor these out in separate files.

For those which are completely re-written, it makes sense to move them
to separate files.

> 4) Short term win. The maintenance will be much simpler avoiding
> the cleanup.

It didn't make sense to keep all the config options for platforms that
would never run Thumb-2 code.

> As you are introducing a new architecture I have added linux-arch
> to list of receivers - maybe someone there has more to say.

I think these patches are in a too early stage at the moment to cc
linux-arch and, if we decide not to go on this route (separate arch),
only discussing on linux-arm-kernel would be enough.

-- 
Catalin


  parent reply	other threads:[~2007-06-06 22:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070606172409.6689.26641.stgit@localhost.localdomain>
2007-06-06 18:29 ` [RFC PATCH 0/9] Thumb-2 ISA kernel port Sam Ravnborg
2007-06-06 20:47   ` Russell King - ARM Linux
2007-06-06 21:10     ` Sam Ravnborg
2007-06-06 21:19       ` Catalin Marinas
2007-06-06 22:04         ` Russell King - ARM Linux
2007-06-06 22:01       ` Russell King - ARM Linux
2007-06-06 22:02   ` Catalin Marinas [this message]
2007-06-07 21:05   ` Ralf Baechle

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=1181167349.27659.49.camel@localhost.localdomain \
    --to=catalin.marinas@arm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=sam@ravnborg.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