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 1/2] arm/mm: L2CC shared mutex with ARM TZ
Date: Wed, 14 Nov 2012 10:50:49 +0000	[thread overview]
Message-ID: <20121114105049.GI3290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <0154077FE026E54BB093CA7EB3FD1AE32DB61E4D23@SAFEX1MAIL3.st.com>

On Wed, Nov 14, 2012 at 11:45:42AM +0100, Etienne CARRIERE ST wrote:
> Thanks for notifying. I will look at the recent release to see if our
> architecture complies with Kernel code.
> 
> Our mutex implementation is based on 0/1 lock/unlock value in target
> mutex DDR cell.

Right, so we have another bug here: it is incompatible with the current
ARM spinlock implementation - and using it on the same memory location
as a spinlock will corrupt the spinlock.

  reply	other threads:[~2012-11-14 10:50 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
2012-11-14 10:45       ` Etienne CARRIERE ST
2012-11-14 10:50         ` Russell King - ARM Linux [this message]
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=20121114105049.GI3290@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).