linux-kernel - linux hardware spinlock framework for heterogeneous processor SOCs?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 11 Aug 2010 21:02:12 -0500
From:	Nishanth Menon <nm@...com>
To:	"Que, Simon" <sque@...com>, LKML <linux-kernel@...r.kernel.org>
CC:	"Kanigeri, Hari" <h-kanigeri2@...com>,
	Linux Omap <linux-omap@...r.kernel.org>,
	Tony Lindgren <tony@...mide.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@...com>,
	"Cousson, Benoit" <b-cousson@...com>
Subject: linux hardware spinlock framework for heterogeneous processor SOCs?

Changing subject, the original thread is at [1], looping in lkml for a 
wider audience for advice.

Que, Simon had written, on 08/11/2010 05:03 PM, the following:
>> just a curious question:
>>
>> Is there no h/w spinlock implementation for other architectures in
>> linux? I mean the concept does not seem unique for a heterogenous
>> processor environments now a days.. if it does exist, maybe we have two
>> options:
>> * extend standard spinlock architecture to handle h/w spinlocks as well
>> * establish a new framework for h/w spinlocks..
>>
> 
> Thank you for bringing that to my attention.  I did a quick search and
 > haven't found any hwspinlock module elsewhere.  But should there be
 > hwspinlocks over multiple architectures in the future, we can definitely
 > consider something like the two solutions that you suggested, so that
 > they can be used from platform-independent kernel code.  However, right
 > now we can develop OMAP hwspinlock independently of that.

I did glance through the kernel commit log, and nothing remotely seems 
to match up at least in my opinion (closest seemed to be [2] 
drivers/gpu/drm/ - but it did not seem relevant here). If this concept 
is unique to OMAP family alone, then I guess it makes sense to introduce 
SOC specific API library for usage. hoping for some suggestions to 
enlighten us.

Ref:
[1] http://marc.info/?t=127955774200003&r=1&w=2
[2] http://dri.sourceforge.net/doc/hardware_locking_low_level.html

-- 
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/