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: [PATCH] ARM: advertise availability of v8 Crypto instructions
Date: Wed, 4 Mar 2015 17:23:53 +0000	[thread overview]
Message-ID: <20150304172353.GC8656@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150304170404.GZ28951@e104818-lin.cambridge.arm.com>

On Wed, Mar 04, 2015 at 05:04:05PM +0000, Catalin Marinas wrote:
> On Wed, Mar 04, 2015 at 05:31:00PM +0100, Ard Biesheuvel wrote:
> > It doesn't really matter which architecture it is. I just want to be
> > reasonably sure that reading ID_ISAR5 isn't going to explode. If there
> > are other/better ways to guarantee that, I am happy to use those as
> > well. (I noticed that there is a v7-M specific definition of ID_ISAR5
> > in the source which I couldn't find any reference to in any of the
> > Cortex-M TRMs on the infocenter web site.)
> 
> The ARMv7-M reference manual only defines to ID_ISAR4. Maybe it will get
> a fifth register at some point but for now I don't think we should read
> it (I guess it was just copy/paste from the A profile).

I think you need to read carefully the requirements that are placed
upon non-implemented CPUID registers.

In DDI0406C, non-implemented CPUID registers are reserved, but must
behave as RAZ.  I would be very surprised if this were not true for
ARMv7-M.


-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-03-04 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 16:36 [PATCH] ARM: advertise availability of v8 Crypto instructions Ard Biesheuvel
2015-03-03 13:43 ` Ard Biesheuvel
2015-03-04 16:20   ` Catalin Marinas
2015-03-04 16:31     ` Ard Biesheuvel
2015-03-04 17:04       ` Catalin Marinas
2015-03-04 17:23         ` Russell King - ARM Linux [this message]
2015-03-04 17:34           ` Catalin Marinas
2015-03-04 17:53             ` Ard Biesheuvel

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=20150304172353.GC8656@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).