All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm/mm: L2CC shared mutex with ARM TZ
Date: Wed, 14 Nov 2012 10:21:27 +0000	[thread overview]
Message-ID: <20121114102127.GH3290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <0154077FE026E54BB093CA7EB3FD1AE32B57AF1E29@SAFEX1MAIL3.st.com>

On Wed, Nov 14, 2012 at 10:18:31AM +0100, Etienne CARRIERE ST wrote:
> > From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk] 
> > Sent: Tuesday, November 13, 2012 6:07 PM
> > 
> > Right, so, what this tells me is that the implementation of the spinlock 
> > in the secure software is potentially the same as the kernel's spinlock.
> > The kernel's spinlock implementation is GPL'd.  If the secure side spinlock 
> > implementation is a copy of the kernel's spinlock implementation, then 
> > that implementation is also GPL'd (...).
> > 
> > I think someone has some explaining to do.
> 
> It does.
> 
> The TZ implementation of the shared mutex is the ARM native mutex
> instructions set LDREX/STREX, protected by a native ARM IRQ disabling.
> I believe this is native ARMv7 natural handling and not subject to
> GPLization.

Maybe, maybe not.  There's more to locking than just the instructions
used - there's the values which are used to represent "locked" and
"unlocked", and then there's the ticket locking implementation found
in recent kernels which defines the value to have more meaning than
just "locked" and "unlocked".

With ticket locking, you need to know the details of the implementation
to be able to lock successfully, and that basically means copying the
implementation.

  parent reply	other threads:[~2012-11-14 10:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 16:08 [PATCH 1/2] arm/mm: L2CC shared mutex with ARM TZ Etienne CARRIERE
2012-11-13 17:07 ` Russell King - ARM Linux
2012-11-14  9:18   ` Etienne CARRIERE ST
2012-11-14  9:51     ` Will Deacon
2012-11-14 10:40       ` Etienne CARRIERE ST
2012-11-14 10:21     ` Russell King - ARM Linux [this message]
2012-11-14 10:45       ` Etienne CARRIERE ST
2012-11-14 10:50         ` Russell King - ARM Linux
2012-11-14 11:02           ` Etienne CARRIERE ST
2012-11-13 17:17 ` Dave Martin
2012-11-13 19:22   ` Abhimanyu Kapur
2012-11-14 10:15     ` Etienne CARRIERE ST
2012-11-14 17:22       ` Catalin Marinas
2012-11-15 13:46         ` Etienne CARRIERE ST
2012-11-15 13:55           ` Catalin Marinas
2012-11-15 14:10             ` Etienne CARRIERE ST
2012-11-14 10:13   ` Etienne CARRIERE ST

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=20121114102127.GH3290@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 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.