linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: questions about arm trustzone
Date: Tue, 25 Jan 2011 12:45:24 +0000	[thread overview]
Message-ID: <20110125124524.GJ11507@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=vZSZkN2k1gZD0F-C74b_jFWX5HhDhr7BiPhN7@mail.gmail.com>

On Tue, Jan 25, 2011 at 12:24:13PM +0000, Dave Martin wrote:
> Avoiding this complexity is one of the motivations for using r7 for
> the syscall number with CONFIG_EABI (instead of using the SVC comment
> field).

Your history is not entirely correct.

I had the kernel side of Thumb userspace support in place long before EABI
came along.  Thumb doesn't have a large enough comment field to store the
Linux syscall number, so to get around that problem, I decided to use r7
for the syscall number.  You'll find 2.4 kernels support Thumb instructions
in userspace.

As part of the EABI switch for ARM mode - which created an incompatible
SWI interface anyway, we decided that we could reduce data cache pollution
by eliminating the read of the SWI instruction, so we adopted the r7
method for ARM EABI mode.

  reply	other threads:[~2011-01-25 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  2:15 questions about arm trustzone sen wang
2011-01-25  7:49 ` David Brown
2011-01-25  9:19   ` sen wang
2011-01-25 10:26     ` Russell King - ARM Linux
2011-01-25 11:46       ` Santosh Shilimkar
2011-01-25 12:00         ` Russell King - ARM Linux
2011-01-25 12:24         ` Dave Martin
2011-01-25 12:45           ` Russell King - ARM Linux [this message]
2011-01-25 13:25             ` Dave Martin
2011-03-11 13:02         ` shiraz hashim

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=20110125124524.GJ11507@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;
as well as URLs for NNTP newsgroup(s).